From: Graham Gower <graham.gower@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] gcc-4.3.3: fix problem with parallel builds.
Date: Tue, 05 Oct 2010 15:53:41 +1030 [thread overview]
Message-ID: <4CAAB65D.1020805@gmail.com> (raw)
The relevant error is as follows.
error: conflicting types for 'strsignal'
| /usr/include/string.h:564: note: previous declaration of 'strsignal' was here
Signed-off-by: Graham Gower <graham.gower@gmail.com>
---
recipes/gcc/gcc-4.3.3.inc | 1 +
recipes/gcc/gcc-4.3.3/Makefile.in.parallel.patch | 21 +++++++++++++++++++++
2 files changed, 22 insertions(+), 0 deletions(-)
create mode 100644 recipes/gcc/gcc-4.3.3/Makefile.in.parallel.patch
diff --git a/recipes/gcc/gcc-4.3.3.inc b/recipes/gcc/gcc-4.3.3.inc
index a3392c0..45520f1 100644
--- a/recipes/gcc/gcc-4.3.3.inc
+++ b/recipes/gcc/gcc-4.3.3.inc
@@ -64,6 +64,7 @@ SRC_URI = "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.bz2;name=archive \
file://gcc-4.3.3-fix-EXTRA_BUILD.patch \
file://arm-gcc-objective.patch \
file://Makefile.in.patch \
+ file://Makefile.in.parallel.patch \
"
SRC_URI_append_sh3 = " file://sh3-installfix-fixheaders.patch "
diff --git a/recipes/gcc/gcc-4.3.3/Makefile.in.parallel.patch b/recipes/gcc/gcc-4.3.3/Makefile.in.parallel.patch
new file mode 100644
index 0000000..d3a7aa1
--- /dev/null
+++ b/recipes/gcc/gcc-4.3.3/Makefile.in.parallel.patch
@@ -0,0 +1,21 @@
+Fix problem with parallel builds failing during build of sparseset.o.
+Upstream: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38591
+
+--- gcc-4_3-branch/gcc/Makefile.in 2010/05/14 12:40:18 159391
++++ gcc-4_3-branch/gcc/Makefile.in 2010/05/14 12:51:31 159392
+@@ -1784,12 +1784,13 @@
+ $(TREE_H) $(FUNCTION_H) $(C_PRAGMA_H) toplev.h output.h $(GGC_H) $(TM_P_H) \
+ $(C_COMMON_H) $(TARGET_H) gt-c-pragma.h $(CPPLIB_H) $(FLAGS_H)
+ graph.o: graph.c $(SYSTEM_H) coretypes.h $(TM_H) toplev.h $(FLAGS_H) output.h \
+- $(RTL_H) $(FUNCTION_H) hard-reg-set.h $(BASIC_BLOCK_H) graph.h $(OBSTACK_H)
++ $(RTL_H) $(FUNCTION_H) hard-reg-set.h $(BASIC_BLOCK_H) graph.h $(OBSTACK_H) \
++ $(CONFIG_H)
+ sbitmap.o: sbitmap.c $(CONFIG_H) $(SYSTEM_H) coretypes.h $(TM_H) $(RTL_H) \
+ $(FLAGS_H) hard-reg-set.h $(BASIC_BLOCK_H) $(OBSTACK_H)
+ ebitmap.o: ebitmap.c $(CONFIG_H) $(SYSTEM_H) coretypes.h $(TM_H) \
+ $(EBITMAP_H)
+-sparseset.o: sparseset.c $(SYSTEM_H) sparseset.h
++sparseset.o: sparseset.c $(SYSTEM_H) sparseset.h $(CONFIG_H)
+
+ COLLECT2_OBJS = collect2.o tlink.o intl.o version.o
+ COLLECT2_LIBS = @COLLECT2_LIBS@
--
1.7.1
reply other threads:[~2010-10-05 5:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CAAB65D.1020805@gmail.com \
--to=graham.gower@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.