From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] mysterious armv5te-linux dir under staging
Date: Sat, 12 Sep 2009 17:04:05 -0700 [thread overview]
Message-ID: <20090913000405.GA29370@gmail.com> (raw)
In-Reply-To: <20090912200308.GA10819@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On (12/09/09 13:03), Khem Raj wrote:
> Hi
>
> On hrw's suggestion I looked into the mysterious directory armv5te-linux
> creation on my omap5912osk build.
>
> This directory is created by staging tasks for cross packages like
> gcc-cross, binutils-cross gdb-cross etc.
>
> This is because in bitbake.conf we set
>
> BASEPKG_HOST_SYS = "${BASE_PACKAGE_ARCH}${HOST_VENDOR}-${HOST_OS}"
>
> which is ok for target recipes but its not ok for native or cross
> recipes.
>
> It works for native because native.bbclass redefines it. I decided
> to change it to
>
>
> BASEPKG_HOST_SYS = "${HOST_ARCH}${HOST_VENDOR}-${HOST_OS}"
>
> HOST_ARCH is defined based on -native -target or -cross package
> so it works in all cases. Overriding in native.bbclass would not
> be needed but I left it in there
It turns out to be that the correct results are obtained if it is
overwrritten in cross.bbclass.
Here is revised patch.
Thanks
-Khem
[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 422 bytes --]
diff --git a/classes/cross.bbclass b/classes/cross.bbclass
index 7debde6..68e3803 100644
--- a/classes/cross.bbclass
+++ b/classes/cross.bbclass
@@ -17,6 +17,7 @@ HOST_OS = "${BUILD_OS}"
HOST_PREFIX = "${BUILD_PREFIX}"
HOST_CC_ARCH = "${BUILD_CC_ARCH}"
HOST_EXEEXT = "${BUILD_EXEEXT}"
+BASEPKG_HOST_SYS = "${HOST_ARCH}${HOST_VENDOR}-${HOST_OS}"
CPPFLAGS = "${BUILD_CPPFLAGS}"
CFLAGS = "${BUILD_CFLAGS}"
next prev parent reply other threads:[~2009-09-13 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 20:03 [RFC] mysterious armv5te-linux dir under staging Khem Raj
2009-09-13 0:04 ` Khem Raj [this message]
2009-09-13 20:29 ` Andrea Adami
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=20090913000405.GA29370@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.