linux-kernel - Re: linux-next: Tree for Mar 31 (build failures and culprits)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <551BE359.2050400@roeck-us.net>
Date:	Wed, 01 Apr 2015 05:23:53 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tony Lindgren <tony@...mide.com>, Felipe Balbi <balbi@...com>,
	Ard Biesheuvel <ard.biesheuvel@...aro.org>,
	Arnd Bergmann <arnd@...db.de>, Lad@...ck-us.net,
	Prabhakar <prabhakar.csengg@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Daniel Mack <daniel@...que.org>,
	Mikko Perttunen <mperttunen@...dia.com>,
	Thierry Reding <treding@...dia.com>
Subject: Re: linux-next: Tree for Mar 31 (build failures and culprits)

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/