From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/4 V2] Share gcc work directories
Date: Wed, 15 Jun 2011 14:33:42 +0800 [thread overview]
Message-ID: <cover.1308108460.git.liezhi.yang@windriver.com> (raw)
Changes of V2:
1) Fix the Makefile.in to read the t-oe in ${B}/gcc/
2) Fix the confiure to read the defaults.in ${B}/gcc/
3) Now the only command that would modify ${S} is gnu-configize, but
this is compatible, it would do nothing in the second run once
config.sub and config.guess were installed to ${S}.
4 I have renamed ${S}/gcc/defaults.h during my testing to confirm that it
really use the one in ${B}/gcc.
5) Here is the rough improvement data:
gcc-cross, gcc-cross-initial and gcc-cross-intermediate will use the
same ${S} and "do_fetch, do_unpack and do_patch", so:
a) $ time bitbake gcc-cross -cpatch -f
real 0m55.742s
so 55s * 2 = 110s will be saved.
b) $ du -sh tmp/work-shared/gcc-4.6.0/
795M tmp/work-shared/gcc-4.6.0/
so 795M * 2 = 1590M (about 1.5G) disk space will be saved.
If we also build gcc-crosssdk, then all the 6 buildings will use
the same ${S}, then:
55s * 5(About 275s) will be saved.
795M * 5 = 3975M(About 3.9G) disk space will be saved.
The following changes since commit 7aa7673459376aff911cef820c9417c998d1aa96:
meta-yocto/linux-yocto: update to match the renamed linux-yocto recipes (2011-06-14 09:21:32 -0700)
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.0: 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 | 34 ++++-----
9 files changed, 199 insertions(+), 23 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-15 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 6:33 Robert Yang [this message]
2011-06-15 6:33 ` [PATCH 1/4 V2] bitbake: share source directory Robert Yang
2011-06-15 6:33 ` [PATCH 2/4 V2] Share gcc work directories Robert Yang
2011-06-15 9:21 ` Richard Purdie
2011-06-15 12:48 ` Robert Yang
2011-06-15 6:33 ` [PATCH 3/4 V2] gcc-4.5.1: share " Robert Yang
2011-06-15 6:33 ` [PATCH 4/4 V2] gcc-4.6.0: " 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.1308108460.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.