All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	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: Tue, 31 Mar 2015 19:17:36 -0700	[thread overview]
Message-ID: <551B5540.60606@roeck-us.net> (raw)
In-Reply-To: <20150331230749.GA6564@kroah.com>

On 03/31/2015 04:07 PM, Greg Kroah-Hartman wrote:
> On Tue, Mar 31, 2015 at 09:16:40AM -0700, Guenter Roeck wrote:
>> On Wed, Apr 01, 2015 at 12:02:21AM +1100, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20150330:
>>>
>>> The arm64 tree gained a conflict against the arm-soc tree.
>>>
>>> The idle tree gained a build failure so I used the version from
>>> next-20150327.
>>>
>>> The tip tree gained conflicts against the pm tree.
>>>
>>> The akpm tree gained a conflict against the mips tree.
>>>
>>> Non-merge commits (relative to Linus' tree): 7277
>>>   6623 files changed, 304342 insertions(+), 138111 deletions(-)
>>>
>>> ----------------------------------------------------------------------------
>>>
>>
>> Build results:
>> 	total: 121 pass: 94 fail: 27
>> Failed builds:
>> 	alpha:allmodconfig
>> 	arm:rpc_defconfig
>> 	arm64:defconfig
>> 	cris:defconfig
>> 	cris:etrax-100lx_defconfig
>> 	cris:allnoconfig
>> 	frv:defconfig
>> 	i386:allyesconfig
>> 	i386:allmodconfig
>> 	ia64:defconfig
>> 	m32r:defconfig
>> 	m68k:defconfig
>> 	m68k:allmodconfig
>> 	m68k:sun3_defconfig
>> 	m68k:m5272c3_defconfig
>> 	m68k:m5307c3_defconfig
>> 	m68k:m5249evb_defconfig
>> 	m68k:m5407c3_defconfig
>> 	m68k:m5475evb_defconfig
>> 	mips:allmodconfig
>> 	parisc:defconfig
>> 	parisc:generic-32bit_defconfig
>> 	parisc:a500_defconfig
>> 	parisc:generic-64bit_defconfig
>> 	x86_64:allyesconfig
>> 	xtensa:defconfig
>> 	xtensa:allmodconfig
>>
>> ---
>> alpha:allmodconfig
>> mips:allmodconfig
>>
>> samples/kdbus/kdbus-workers.c: In function ‘prime_new’:
>> samples/kdbus/kdbus-workers.c:930:18: error: ‘__NR_memfd_create’ undeclared
>> (first use in this function)
>>    p->fd = syscall(__NR_memfd_create, "prime-area", MFD_CLOEXEC);
>>
>> Looks like the kdbus example never worked for the affected architectures.
>> I don't build allmodconfig for all architectures, so other architectures
>> may be affected as well.
>
> 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.

Guenter

  parent reply	other threads:[~2015-04-01  2:17 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 [this message]
2015-04-01  8:08       ` Russell King - ARM Linux
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=551B5540.60606@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=mperttunen@nvidia.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.