From: Michael Ellerman <mpe@ellerman•id.au>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: dh.herrmann@googlemail•com, gregkh@linuxfoundation•org,
daniel@zonque•org, tixxdz@opendz•org, linux-mips@linux-mips•org,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Subject: Re: samples/kdbus/kdbus-workers.c and cross compiling MIPS
Date: Thu, 30 Jul 2015 11:28:07 +1000 [thread overview]
Message-ID: <1438219687.2374.1.camel@ellerman.id.au> (raw)
In-Reply-To: <20150729161912.GF18685@windriver.com>
On Wed, 2015-07-29 at 12:19 -0400, Paul Gortmaker wrote:
> Hi David,
>
> Does it make sense to build this sample when cross compiling?
>
> The reason I ask is that it has been breaking the linux-next build of
> allmodconfig for a while now, with:
>
> HOSTCC samples/kdbus/kdbus-workers
> samples/kdbus/kdbus-workers.c: In function ‘prime_new’:
> samples/kdbus/kdbus-workers.c:934:18: error: ‘__NR_memfd_create’ undeclared (first use in this function)
> p->fd = syscall(__NR_memfd_create, "prime-area", MFD_CLOEXEC);
> ^
> samples/kdbus/kdbus-workers.c:934:18: note: each undeclared identifier is reported only once for each function it appears in
> scripts/Makefile.host:91: recipe for target 'samples/kdbus/kdbus-workers' failed
> make[2]: *** [samples/kdbus/kdbus-workers] Error 1
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12473453/
>
> We recently made some changes to skip other sample/test programs when
> cross compiling in mainline 65f6f092a6987 and f59514b6a8c5ca6dd and
> 6a407a81a9abcf. Maybe it makes sense to do the same here?
Hi Paul,
We also can configure kisskb to not build samples for all_modconfig, which
avoids these sort of issues with a slight decrease in code coverage. We already
disable samples for several other arch all_modconfigs.
cheers
prev parent reply other threads:[~2015-07-30 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 16:19 samples/kdbus/kdbus-workers.c and cross compiling MIPS Paul Gortmaker
2015-07-29 16:31 ` David Herrmann
2015-07-30 13:50 ` Paul Gortmaker
2015-07-30 14:23 ` David Herrmann
2015-07-30 15:32 ` Paul Gortmaker
2015-07-30 23:55 ` Stephen Rothwell
2015-07-31 6:54 ` Michael Ellerman
2015-07-31 7:01 ` Michael Ellerman
2015-07-31 16:29 ` Greg Kroah-Hartman
2015-08-03 4:58 ` Michael Ellerman
2015-07-30 1:28 ` Michael Ellerman [this message]
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=1438219687.2374.1.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=daniel@zonque$(echo .)org \
--cc=dh.herrmann@googlemail$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mips@linux-mips$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=tixxdz@opendz$(echo .)org \
/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