All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <dh.herrmann@googlemail.com>
Cc: <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: samples/kdbus/kdbus-workers.c and cross compiling MIPS
Date: Wed, 29 Jul 2015 12:19:12 -0400	[thread overview]
Message-ID: <20150729161912.GF18685@windriver.com> (raw)

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?

Paul.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: dh.herrmann@googlemail.com
Cc: 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: samples/kdbus/kdbus-workers.c and cross compiling MIPS
Date: Wed, 29 Jul 2015 12:19:12 -0400	[thread overview]
Message-ID: <20150729161912.GF18685@windriver.com> (raw)
Message-ID: <20150729161912.hyNsN8rLQOnVW1n_MXDBSW1sa1F4U73y65TEBiExPxI@z> (raw)

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?

Paul.

             reply	other threads:[~2015-07-29 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 16:19 Paul Gortmaker [this message]
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 13:50     ` Paul Gortmaker
2015-07-30 14:23     ` David Herrmann
2015-07-30 15:32       ` Paul Gortmaker
2015-07-30 15:32         ` Paul Gortmaker
2015-07-30 23:55         ` Stephen Rothwell
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

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=20150729161912.GF18685@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=daniel@zonque.org \
    --cc=dh.herrmann@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tixxdz@opendz.org \
    /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.