Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: about ${KERNEL_CC} and ${CC}
Date: Thu, 23 Dec 2010 05:27:08 -0700	[thread overview]
Message-ID: <4D13401C.8080901@mlbassoc.com> (raw)
In-Reply-To: <1293097470.1588.567.camel@rex>

[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]

On 12/23/2010 02:44 AM, Richard Purdie wrote:
> On Thu, 2010-12-23 at 14:11 +0800, Tian, Kevin wrote:
>> I'm a bit confused why a specific ${KERNEL_CC} is introduced instead of
>> reusing ${CC}, especially when two are defined differently:
>>
>> <kernel.bbclass>
>> KERNEL_CC = "${CCACHE}${HOST_PREFIX}gcc${KERNEL_CCSUFFIX} ${HOST_CC_KERNEL_ARCH}"
>>
>> <bitbake.conf>
>> export CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}"
>> TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
>>
>> I'm not sure whether kernel build requires "--sysroot" option, but it looks that it works well
>> so far even without that option (why?)
>
> The kernel doesn't link against system libraries or use system header
> files so it really doesn't matter whether it sees the sysroot or not.
>
> We use a different CC for the kernel so the user has the option of using
> a different compiler version for this. Whilst its a lot less common now,
> there were once use cases where the kernel would be compiled with one
> version of gcc and the userspace with a different version.
>
>> However this causes one issue under sstate, if the whole toolchain is installed from sstate
>> packages which are built from another machine. In such case the default path (decided at
>> compilation time) of gcc also points to the path on another machine, which is missing in
>> current machine doing build. Perf compilation is:
>>
>> do_compile_perf() {
>>          oe_runmake -C ${S}/tools/perf CC="${KERNEL_CC}" LD="${KERNEL_LD}" prefix=${prefix}
>> }
>>
>> Without an explicit "--sysroot" options, perf compilation is broken due to failing to check some
>> header files like gnu/libc-version.h. I can workaround it by:
>>
>> do_compile_perf() {
>>          oe_runmake -C ${S}/tools/perf CC="${CC}" LD="${LD}" AR="${AR}" prefix=${prefix}
>> }
>
> Perf should be compiled with the userspace toolchain, not the kernel
> one. I'd say this fix is therefore correct.
>
> Adding TOOLCHAIN_OPTIONS to KERNEL_CC would also probably be a good idea
> too.

Perfect idea!  I added this and I'm now able to rebuild my
kernel package using a sstate-cache based toolchain.  This
should close bug #605

Patch attached for review.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: 0001-Include-sysroot-in-KERNEL_CC-allows-tools-to-move.patch --]
[-- Type: text/plain, Size: 1076 bytes --]

From 316c5f347106f4edb3d72818025916cac164d526 Mon Sep 17 00:00:00 2001
From: Gary Thomas <gary@mlbassoc.com>
Date: Thu, 23 Dec 2010 05:20:20 -0700
Subject: [PATCH] Include --sysroot in ${KERNEL_CC} - allows tools to move

Signed-off-by: Gary Thomas <gary@mlbassoc.com>
---
 meta/classes/kernel.bbclass |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 26273bd..f380a5c 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -40,7 +40,8 @@ HOST_CC_KERNEL_ARCH ?= "${TARGET_CC_KERNEL_ARCH}"
 TARGET_LD_KERNEL_ARCH ?= ""
 HOST_LD_KERNEL_ARCH ?= "${TARGET_LD_KERNEL_ARCH}"
 
-KERNEL_CC = "${CCACHE}${HOST_PREFIX}gcc${KERNEL_CCSUFFIX} ${HOST_CC_KERNEL_ARCH}"
+KERNEL_CC = "${CCACHE}${HOST_PREFIX}gcc${KERNEL_CCSUFFIX} ${HOST_CC_KERNEL_ARCH} ${TOOLCHAIN_OPTIONS}"
+TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
 KERNEL_LD = "${LD}${KERNEL_LDSUFFIX} ${HOST_LD_KERNEL_ARCH}"
 
 # Where built kernel lies in the kernel tree
-- 
1.7.2.3


  reply	other threads:[~2010-12-23 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  6:11 about ${KERNEL_CC} and ${CC} Tian, Kevin
2010-12-23  9:44 ` Richard Purdie
2010-12-23 12:27   ` Gary Thomas [this message]
2010-12-24  1:01     ` Tian, Kevin
2010-12-30 10:21     ` Richard Purdie
2010-12-30 18:02       ` Gary Thomas

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=4D13401C.8080901@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@pokylinux.org \
    --cc=richard.purdie@linuxfoundation.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