From: Guenter Roeck <linux@roeck-us.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tony Lindgren <tony@atomide.com>, Felipe Balbi <balbi@ti.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Lad@roeck-us.net, Prabhakar <prabhakar.csengg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Mack <daniel@zonque.org>,
Mikko Perttunen <mperttunen@nvidia.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: linux-next: Tree for Mar 31 (build failures and culprits)
Date: Wed, 01 Apr 2015 05:23:53 -0700 [thread overview]
Message-ID: <551BE359.2050400@roeck-us.net> (raw)
In-Reply-To: <20150401080806.GY24899@n2100.arm.linux.org.uk>
On 04/01/2015 01:08 AM, Russell King - ARM Linux wrote:
> On Tue, Mar 31, 2015 at 07:17:36PM -0700, Guenter Roeck wrote:
>> On 03/31/2015 04:07 PM, Greg Kroah-Hartman wrote:
>>> You need 3.17 kernel headers to have memfd_create, not much the kdbus
>>> test code can do about that. You might want to update the kernel
>>> headers for these build boxes.
>>>
>>
>> Seems there are brand-new requirements for kernel builds. The toolchain determines
>> the headers used, not the native kernel (which, FWIW, is 3.19). You might want
>> to document somewhere that "allmodconfig" and possibly "allyesconfig" now only
>> builds if the toolchain is based on 3.17+ kernel headers.
>>
>> I think I'll just drop those allmodconfig builds instead, or find a means to drop
>> the samples/kdbus builds. Sorry, my time is limited. Building toolchains costs a
>> lot of time, which I simply don't have. Keep in mind that I am doing all this on
>> my own spare time. You are putting a lot of burden on people doing test builds.
>
> You _can_ avoid it by seeding those configurations. You place the
> options you want to force to a specific value in a file, and then
> do:
>
> make allmodconfig KCONFIG_ALLCONFIG=seed-config-file
>
> So, to turn off samples:
>
> CONFIG_SAMPLES=n
>
> in seed-config-file. Hence, you can still do an allmodconfig build but
> without building the samples subdir.
>
I am doing it more complicated (so far), by using sed to manipulate the config file
after it was created, but that is better - I'll switch to that method.
Thanks!
Guenter
next prev parent reply other threads:[~2015-04-01 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 13:02 linux-next: Tree for Mar 31 Stephen Rothwell
2015-03-31 16:16 ` linux-next: Tree for Mar 31 (build failures and culprits) Guenter Roeck
2015-03-31 23:07 ` Greg Kroah-Hartman
2015-03-31 23:24 ` Michael Ellerman
2015-04-01 2:18 ` Guenter Roeck
2015-04-01 3:01 ` Michael Ellerman
2015-04-01 3:13 ` Guenter Roeck
2015-03-31 23:42 ` Stephen Rothwell
2015-04-01 2:24 ` Guenter Roeck
2015-04-01 2:45 ` Guenter Roeck
2015-04-01 6:13 ` Daniel Mack
2015-04-01 2:17 ` Guenter Roeck
2015-04-01 8:08 ` Russell King - ARM Linux
2015-04-01 12:23 ` Guenter Roeck [this message]
2015-04-01 3:16 ` Max Filippov
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=551BE359.2050400@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Lad@roeck-us.net \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=daniel@zonque.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mperttunen@nvidia.com \
--cc=prabhakar.csengg@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=treding@nvidia.com \
/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 NNTP newsgroup(s).