From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: saul.wold@intel.com
Subject: [PATCH V3 0/1] gcc-4.9.inc: fix parallel building failure
Date: Tue, 29 Jul 2014 10:02:01 +0800 [thread overview]
Message-ID: <cover.1406598828.git.hongxu.jia@windriver.com> (raw)
Changed in V3:
Rebase it against master as we have already
merged the first version.
Change in V2:
As the upstream of gcc suggested:
- The previous fix is too hack;
- Use '$(ALL_HOST_OBJS) : | $(generated_files)' rule to
handle the dependency.
Test Steps:
1. For reproducing the issue every time, manually modify
gcc/Makefile.in to delay the generation of config.h:
...
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index c4daf69..c502898 100644
--- gcc-4.9.0/gcc/Makefile.in
+++ gcc-4.9.0/gcc/Makefile.in
@@ -1622,9 +1622,12 @@ tm.h: cs-tm.h ; @true
tm_p.h: cs-tm_p.h ; @true
cs-config.h: Makefile
+ @echo "start to generate config.h `date`"
+ sleep 10
TARGET_CPU_DEFAULT="" \
HEADERS="$(host_xm_include_list)" DEFINES="$(host_xm_defines)" \
$(SHELL) $(srcdir)/mkconfig.sh config.h
+ @echo "config.h generated `date`"
cs-bconfig.h: Makefile
TARGET_CPU_DEFAULT="" \
...
2. bitbake gcc-cross-arm
//Hongxu
The following changes since commit addeef1dc91306175824b1f5587e40a22773cff4:
lib/oe/rootfs: Improve error message whitespace (2014-07-28 12:21:24 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-gcc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/fix-gcc
Hongxu Jia (1):
gcc-4.9.inc: fix parallel building failure
...Makefile.in-fix-parallel-building-failure.patch | 79 ++++++++++++----------
1 file changed, 42 insertions(+), 37 deletions(-)
--
1.8.1.2
next reply other threads:[~2014-07-29 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 2:02 Hongxu Jia [this message]
2014-07-29 2:02 ` [PATCH 1/1] gcc-4.9.inc: fix parallel building failure Hongxu Jia
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.1406598828.git.hongxu.jia@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/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.