From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] FW: [PATCH] linux-headers: cross compile fix
Date: Sun, 23 Feb 2014 10:50:41 +0100 [thread overview]
Message-ID: <20140223105041.414123e2@skate> (raw)
In-Reply-To: <884EA965490E3C4D8E66AEF41E98025006BF4D@ezex10.ezchip.com>
Dear Noam Camus,
On Sun, 23 Feb 2014 08:29:15 +0000, Noam Camus wrote:
> Otherwise compiler not found errors occured.
>
> Signed-off-by: Noam Camus <noamc@ezchip.com>
> ---
> package/linux-headers/linux-headers.mk | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/package/linux-headers/linux-headers.mk b/package/linux-headers/linux-headers.mk
> index 30d3076..632b94f 100644
> --- a/package/linux-headers/linux-headers.mk
> +++ b/package/linux-headers/linux-headers.mk
> @@ -25,6 +25,7 @@ define LINUX_HEADERS_INSTALL_STAGING_CMDS
> HOSTCFLAGS="$(HOSTCFLAGS)" \
> HOSTCXX="$(HOSTCXX)" \
> INSTALL_HDR_PATH=$(STAGING_DIR)/usr \
> + CROSS_COMPILE="$(TARGET_CROSS)" \
> headers_install)
> endef
>
Doesn't look harmful in principle, but it seems to have worked until
now without CROSS_COMPILE="$(TARGET_CROSS)". Can you expand the commit
log by explaining in which case you have seen errors, and which errors.
The linux-headers package is used daily to build toolchains by all
Buildroot users, so I'd like to understand how your situation is
different. Is it that the ARC kernel headers need something special?
But we are building ARC toolchains everyday in the autobuilders, with
no problem. That's why I'd like to have more details.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-23 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 8:29 [Buildroot] FW: [PATCH] linux-headers: cross compile fix Noam Camus
2014-02-23 9:50 ` Thomas Petazzoni [this message]
2014-02-23 12:33 ` Noam Camus
2014-02-23 14:11 ` Thomas Petazzoni
2014-02-23 14:13 ` Yann E. MORIN
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=20140223105041.414123e2@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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