From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/6 V3] Share gcc work directories
Date: Sat, 18 Jun 2011 20:41:30 +0800 [thread overview]
Message-ID: <cover.1308391365.git.liezhi.yang@windriver.com> (raw)
Changes of V3:
1) Use --with-headers to replace the:
sed -i 's:^\([ ]*\)glibc_header_dir=\"${with_build_sysroot}/usr/include\": ...
2) Fix the build of gcc-cross-canadian
3) Fix gcc-crosssdk which make the source incompatible during its
building.
4) Test "bitbake meta-toolchain", and also do run test for the
pokysdk(unpack the toolchain to /opt, setup the env by sourcing
environment-setup-armv5te-poky-linux-gnueabi, and build some pkgs
out of poky, then use command file to check the binary file type.
5) Make sure that no gcc build would make the source incompatible,
except gcc-cross_csl-arm-2008q1.bb, but I think this is fine, its
BINV = "4.2.3", not 4.5.1 or 4.6.0.
Thanks for Richard's great help.
// Robert
The following changes since commit 2163461ec94528ecf046a04edc5db3d2dd3a6b8b:
systemtap: remove non-core COMPATIBLE_MACHINES (2011-06-16 22:14:06 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib robert/share_gcc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/share_gcc
Robert Yang (6):
bitbake: share source directory
Share gcc work directories
gcc-4.5.1: share work directories
gcc-4.6.0: share work directories
gcc-crosssdk: share work directories
gcc-cross-canadian: share work directories
bitbake/lib/bb/build.py | 4 +-
bitbake/lib/bb/cache.py | 3 +
bitbake/lib/bb/runqueue.py | 10 +++
meta/recipes-devtools/gcc/gcc-4.5.1.inc | 1 +
.../gcc-4.5.1/use-defaults.h-and-t-oe-in-B.patch | 57 ++++++++++++++
meta/recipes-devtools/gcc/gcc-4.6.0.inc | 1 +
.../gcc-4.6.0/use-defaults.h-and-t-oe-in-B.patch | 80 ++++++++++++++++++++
meta/recipes-devtools/gcc/gcc-common.inc | 32 +++++++-
meta/recipes-devtools/gcc/gcc-configure-common.inc | 33 ++++-----
meta/recipes-devtools/gcc/gcc-configure-cross.inc | 4 +-
meta/recipes-devtools/gcc/gcc-configure-sdk.inc | 8 ++
meta/recipes-devtools/gcc/gcc-crosssdk.inc | 13 +++-
12 files changed, 220 insertions(+), 26 deletions(-)
create mode 100644 meta/recipes-devtools/gcc/gcc-4.5.1/use-defaults.h-and-t-oe-in-B.patch
create mode 100644 meta/recipes-devtools/gcc/gcc-4.6.0/use-defaults.h-and-t-oe-in-B.patch
next reply other threads:[~2011-06-18 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 12:41 Robert Yang [this message]
2011-06-18 12:41 ` [PATCH 1/6 V3] bitbake: share source directory Robert Yang
2011-06-18 12:41 ` [PATCH 2/6 V3] Share gcc work directories Robert Yang
2011-06-18 12:41 ` [PATCH 3/6 V3] gcc-4.5.1: share " Robert Yang
2011-06-18 12:41 ` [PATCH 4/6 V3] gcc-4.6.0: " Robert Yang
2011-06-18 12:41 ` [PATCH 5/6 V3] gcc-crosssdk: " Robert Yang
2011-06-22 18:55 ` Richard Purdie
2011-06-23 2:01 ` Robert Yang
2011-06-18 12:41 ` [PATCH 6/6 V3] gcc-cross-canadian: " Robert Yang
2011-06-18 12:50 ` [PATCH 0/6 V3] Share gcc " Koen Kooi
2011-06-20 1:48 ` Robert Yang
2011-06-20 21:01 ` Khem Raj
2011-06-21 1:27 ` Robert Yang
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=cover.1308391365.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox