From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Herrmann <dh.herrmann@gmail.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Daniel Mack <daniel@zonque.org>,
Djalal Harouni <tixxdz@opendz.org>
Subject: Re: [PATCH] kdbus/samples: skip on CROSS_COMPILE
Date: Thu, 30 Jul 2015 09:33:07 -0700 [thread overview]
Message-ID: <20150730163307.GA20048@kroah.com> (raw)
In-Reply-To: <1438272805-19029-1-git-send-email-dh.herrmann@gmail.com>
On Thu, Jul 30, 2015 at 06:13:25PM +0200, David Herrmann wrote:
> Apparently we cannot rely on up-to-date kernel headers to be available
> when cross-compiling, not even for HOSTCC. That's sad, but it's how it
> is. Skip samples on cross-compiles as suggested by Paul, so allmodconfig
> runs smoothly again.
>
> Tested-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
> ---
> samples/kdbus/Makefile | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/samples/kdbus/Makefile b/samples/kdbus/Makefile
> index 137f842..dbd9de8 100644
> --- a/samples/kdbus/Makefile
> +++ b/samples/kdbus/Makefile
> @@ -1,9 +1,13 @@
> # kbuild trick to avoid linker error. Can be omitted if a module is built.
> obj- := dummy.o
>
> +ifndef CROSS_COMPILE
This really feels like the wrong solution.
> +
> hostprogs-$(CONFIG_SAMPLE_KDBUS) += kdbus-workers
>
> always := $(hostprogs-y)
>
> HOSTCFLAGS_kdbus-workers.o += -I$(objtree)/usr/include
> HOSTLOADLIBES_kdbus-workers := -lrt
> +
> +endif
Shuah, how should we fix this "properly"? How is this resolved for the
kernel test scripts, it should have the same issue that the samples do.
thanks,
greg k-h
next prev parent reply other threads:[~2015-07-30 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 16:13 [PATCH] kdbus/samples: skip on CROSS_COMPILE David Herrmann
2015-07-30 16:33 ` Greg Kroah-Hartman [this message]
2015-07-30 17:00 ` David Herrmann
2015-07-30 17:00 ` Paul Gortmaker
2015-07-31 14:28 ` Sudip Mukherjee
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=20150730163307.GA20048@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=shuahkh@osg.samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox