From: Filipe Brandenburger <filbranden@google.com>
To: Rick Zero_Chaos Farina <zerochaos@gentoo.org>
Cc: linux-numa@vger.kernel.org
Subject: Re: [PATCH] fix numactl test
Date: Tue, 5 May 2015 08:55:44 -0700 [thread overview]
Message-ID: <CADU+-uB0T3L5qMbpBEVNWvL1OSXRCS079Bq19HHSscHeVBvX_g@mail.gmail.com> (raw)
In-Reply-To: <554847E7.7080300@gentoo.org>
Hi Rick,
On Mon, May 4, 2015 at 9:32 PM, Rick "Zero_Chaos" Farina
<zerochaos@gentoo.org> wrote:
> 2.0.10 has a bug related to gentoo which I haven't figured out yet
> (doesn't appear to be upstream related afaict so far so don't worry
> about it)
Do you have a Gentoo bug tracking the issue?
2.0.10 was the first version that switched the build to use autotools
so the .ebuild probably needs to be updated to include a call to
./configure in the build process...
Cheers,
Filipe
prev parent reply other threads:[~2015-05-05 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 2:35 [PATCH] fix numactl test Rick "Zero_Chaos" Farina
2015-05-04 20:29 ` Filipe Brandenburger
2015-05-05 4:32 ` Rick "Zero_Chaos" Farina
2015-05-05 15:55 ` Filipe Brandenburger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADU+-uB0T3L5qMbpBEVNWvL1OSXRCS079Bq19HHSscHeVBvX_g@mail.gmail.com \
--to=filbranden@google.com \
--cc=linux-numa@vger.kernel.org \
--cc=zerochaos@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).