From: Russell King - ARM Linux <linux@arm•linux.org.uk>
To: Guenter Roeck <linux@roeck-us•net>
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, 1 Apr 2015 09:08:06 +0100 [thread overview]
Message-ID: <20150401080806.GY24899@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <551B5540.60606@roeck-us.net>
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.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-04-01 8:08 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 [this message]
2015-04-01 12:23 ` Guenter Roeck
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=20150401080806.GY24899@n2100.arm.linux.org.uk \
--to=linux@arm$(echo .)linux.org.uk \
--cc=Lad@roeck-us$(echo .)net \
--cc=ard.biesheuvel@linaro$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=balbi@ti$(echo .)com \
--cc=daniel@zonque$(echo .)org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=mperttunen@nvidia$(echo .)com \
--cc=prabhakar.csengg@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=tony@atomide$(echo .)com \
--cc=treding@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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