From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/4 V4] Share gcc work directories
Date: Tue, 28 Jun 2011 17:05:18 +0800 [thread overview]
Message-ID: <cover.1309243115.git.liezhi.yang@windriver.com> (raw)
Changes of V4:
* Change the definition of GLIBC_DYNAMIC_LINKER as Richard suggested.
e.g., the entries in the files that look like:
#define GLIBC_DYNAMIC_LINKER64 "/lib64/ld-linux-x86-64.so.2"
become
#define GLIBC_DYNAMIC_LINKER64 SYSTEMLIBS_DIR"/ld-linux-x86-64.so.2"
and we define SYSTEMLIBS_DIR in defaults.h.
NOTE, the round brackets:
#define GLIBC_DYNAMIC_LINKER64 (SYSTEMLIBS_DIR "/ld-linux-x86-64.so.2")
doesn't work in in the following define:
#define LINUX_DYNAMIC_LINKER \
CHOOSE_DYNAMIC_LINKER (GLIBC_DYNAMIC_LINKER, UCLIBC_DYNAMIC_LINKER)
so use:
#define GLIBC_DYNAMIC_LINKER64 SYSTEMLIBS_DIR"/ld-linux-x86-64.so.2"
* Compare to V3, reduce two patches which are for gcc-crosssdk.inc and
gcc-cross-canadian which are not needed any more.
* Fix the conflicts(gcc-4.6.0 -> gcc-4.6, and the ${BRANCH})
* Both tested 4.5.1 and 4.6:
$ bitbake meta-toolchain core-image-sato
$ runqemu qemurm
Also unpack the sdk to /opt and test to make sure the toolchain works well.
The following changes since commit a1f79a7896b6411669b3ccada6204d2695e80fc5:
runqueue.py: Add umask task control (2011-06-24 12:23:12 +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 (4):
bitbake: share source directory
Share gcc work directories
gcc-4.5.1: share work directories
gcc-4.6: 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.inc | 5 +-
.../gcc/gcc-4.6/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 | 48 +++++++-----
meta/recipes-devtools/gcc/gcc-configure-cross.inc | 4 +-
meta/recipes-devtools/gcc/gcc-crosssdk.inc | 6 --
11 files changed, 218 insertions(+), 32 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/use-defaults.h-and-t-oe-in-B.patch
next reply other threads:[~2011-06-28 9:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 9:05 Robert Yang [this message]
2011-06-28 9:05 ` [PATCH 1/4 V4] bitbake: share source directory Robert Yang
2011-06-28 11:19 ` Richard Purdie
2011-06-28 9:05 ` [PATCH 2/4 V4] Share gcc work directories Robert Yang
2011-06-28 9:05 ` [PATCH 3/4 V4] gcc-4.5.1: share " Robert Yang
2011-06-28 9:05 ` [PATCH 4/4 V4] gcc-4.6: " Robert Yang
2011-06-28 14:53 ` [PATCH 0/4 V4] Share gcc " Richard Purdie
2011-06-30 23:26 ` Saul Wold
2011-07-01 7:15 ` It's broken, please revert. " Koen Kooi
2011-07-01 8:10 ` Richard Purdie
2011-07-01 9:08 ` Koen Kooi
2011-07-01 11:28 ` Richard Purdie
2011-07-01 8:32 ` Richard Purdie
2011-07-01 11:00 ` Koen Kooi
2011-07-01 13:57 ` Khem Raj
2011-07-01 14:01 ` Koen Kooi
2011-07-01 16:55 ` Khem Raj
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.1309243115.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 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.