From: Guenter Roeck <linux@roeck-us•net>
To: Michael Ellerman <mpe@ellerman•id.au>,
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:18:34 -0700 [thread overview]
Message-ID: <551B557A.40805@roeck-us.net> (raw)
In-Reply-To: <1427844281.4256.3.camel@ellerman.id.au>
On 03/31/2015 04:24 PM, Michael Ellerman wrote:
> On Wed, 2015-04-01 at 01:07 +0200, Greg Kroah-Hartman wrote:
>> On Tue, Mar 31, 2015 at 09:16:40AM -0700, Guenter Roeck wrote:
>>> 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.
>
> Or just 'make headers_install' before building the samples should do it.
>
Sure, that works so well in a cross build environment.
Guenter
next prev parent reply other threads:[~2015-04-01 2:18 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 [this message]
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
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=551B557A.40805@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--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=mpe@ellerman$(echo .)id.au \
--cc=mperttunen@nvidia$(echo .)com \
--cc=prabhakar.csengg@gmail$(echo .)com \
--cc=rmk+kernel@arm$(echo .)linux.org.uk \
--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