From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] mysterious armv5te-linux dir under staging
Date: Sat, 12 Sep 2009 13:03:08 -0700 [thread overview]
Message-ID: <20090912200308.GA10819@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
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
Does anyone sees problem with this little patchlet ?
Thanks
-Khem
[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 676 bytes --]
diff --git a/conf/bitbake.conf b/conf/bitbake.conf
index c2f7666..24684e5 100644
--- a/conf/bitbake.conf
+++ b/conf/bitbake.conf
@@ -114,7 +114,7 @@ PACKAGE_ARCHS = "all any noarch ${TARGET_ARCH} ${PACKAGE_EXTRA_ARCHS} ${MACHINE}
MULTIMACH_ARCH = "${PACKAGE_ARCH}"
MULTIMACH_TARGET_SYS = "${MULTIMACH_ARCH}${TARGET_VENDOR}-${TARGET_OS}"
MULTIMACH_HOST_SYS = "${MULTIMACH_ARCH}${HOST_VENDOR}-${HOST_OS}"
-BASEPKG_HOST_SYS = "${BASE_PACKAGE_ARCH}${HOST_VENDOR}-${HOST_OS}"
+BASEPKG_HOST_SYS = "${HOST_ARCH}${HOST_VENDOR}-${HOST_OS}"
BASEPKG_TARGET_SYS = "${BASE_PACKAGE_ARCH}${TARGET_VENDOR}-${TARGET_OS}"
# select proper CPU to get binary locales generated
next reply other threads:[~2009-09-12 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 20:03 Khem Raj [this message]
2009-09-13 0:04 ` [RFC] mysterious armv5te-linux dir under staging Khem Raj
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=20090912200308.GA10819@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.