From: Saul Wold <sgw@linux.intel.com>
To: Hongxu Jia <hongxu.jia@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] gcc-4.9.inc: fix parallel building failure
Date: Fri, 25 Jul 2014 08:48:38 -0700 [thread overview]
Message-ID: <53D27C56.9020600@linux.intel.com> (raw)
In-Reply-To: <9744f54022b591228ed2566f8d5fa3b3c97f6ca9.1406275654.git.hongxu.jia@windriver.com>
Can you please rebase this against master as we have already merged the
first version.
Thanks
Sau!
On 07/25/2014 03:13 AM, Hongxu Jia wrote:
> The gcc-ar.o, gcc-nm.o, gcc-ranlib.o and errors.o included
> config.h which was a generated file. But no explicity rule
> to clarify the dependency. There was potential building
> failure while parallel make.
>
> For gcc-ar.o, gcc-nm.o and gcc-ranlib.o, they were compiled from one C
> source file gcc-ar.c, we add them to ALL_HOST_BACKEND_OBJS, so the
> '$(ALL_HOST_OBJS) : | $(generated_files)' rule could work for these
> objects.
>
> For errors.o, it is part of gengtype, and the gengtype generator program
> is special: Two versions are built. One is for the build machine, and one
> is for the host. We refered what gengtype-parse.o did (which also is part
> of gengtype).
>
> [YOCTO #6568]
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> meta/recipes-devtools/gcc/gcc-4.9.inc | 1 +
> ...Makefile.in-fix-parallel-building-failure.patch | 64 ++++++++++++++++++++++
> 2 files changed, 65 insertions(+)
> create mode 100644 meta/recipes-devtools/gcc/gcc-4.9/0054-gcc-Makefile.in-fix-parallel-building-failure.patch
>
> diff --git a/meta/recipes-devtools/gcc/gcc-4.9.inc b/meta/recipes-devtools/gcc/gcc-4.9.inc
> index cbf1355..10bd5d5 100644
> --- a/meta/recipes-devtools/gcc/gcc-4.9.inc
> +++ b/meta/recipes-devtools/gcc/gcc-4.9.inc
> @@ -67,6 +67,7 @@ SRC_URI = "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.bz2 \
> file://0051-eabispe.patch \
> file://0052-Fix-GCC-targeting-E500-SPE-errors-with-the-_Decimal64-type.patch \
> file://0053-gcc-fix-segfault-from-calling-free-on-non-malloc-d-a.patch \
> + file://0054-gcc-Makefile.in-fix-parallel-building-failure.patch \
> "
> SRC_URI[md5sum] = "9709b49ae0e904cbb0a6a1b62853b556"
> SRC_URI[sha256sum] = "b9b047a97bade9c1c89970bc8e211ff57b7b8998a1730a80a653d329f8ed1257"
> diff --git a/meta/recipes-devtools/gcc/gcc-4.9/0054-gcc-Makefile.in-fix-parallel-building-failure.patch b/meta/recipes-devtools/gcc/gcc-4.9/0054-gcc-Makefile.in-fix-parallel-building-failure.patch
> new file mode 100644
> index 0000000..6277bec
> --- /dev/null
> +++ b/meta/recipes-devtools/gcc/gcc-4.9/0054-gcc-Makefile.in-fix-parallel-building-failure.patch
> @@ -0,0 +1,64 @@
> +From 5a50cebd00930930e609e978331ede690f34512b Mon Sep 17 00:00:00 2001
> +From: Hongxu Jia <hongxu.jia@windriver.com>
> +Date: Fri, 25 Jul 2014 14:35:17 +0800
> +Subject: [PATCH] gcc/Makefile.in: fix parallel building failure
> +
> +The gcc-ar.o, gcc-nm.o, gcc-ranlib.o and errors.o included
> +config.h which was a generated file. But no explicity rule
> +to clarify the dependency. There was potential building
> +failure while parallel make.
> +
> +For gcc-ar.o, gcc-nm.o and gcc-ranlib.o, they were compiled from one C
> +source file gcc-ar.c, we add them to ALL_HOST_BACKEND_OBJS, so the
> +'$(ALL_HOST_OBJS) : | $(generated_files)' rule could work for these
> +objects.
> +
> +For errors.o, it is part of gengtype, and the gengtype generator program
> +is special: Two versions are built. One is for the build machine, and one
> +is for the host. We refered what gengtype-parse.o did (which also is part
> +of gengtype).
> +
> +[GCC #61899]
> +https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61899
> +
> +Upstream-Status: Send to gcc-patches@gcc.gnu.org mailing list
> +
> +Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> +---
> + gcc/Makefile.in | 7 ++++++-
> + 1 file changed, 6 insertions(+), 1 deletion(-)
> +
> +diff --git a/gcc/Makefile.in b/gcc/Makefile.in
> +index 6475cba..56e50bb 100644
> +--- a/gcc/Makefile.in
> ++++ b/gcc/Makefile.in
> +@@ -1481,13 +1481,16 @@ OBJS-libcommon-target = $(common_out_object_file) prefix.o params.o \
> + opts.o opts-common.o options.o vec.o hooks.o common/common-targhooks.o \
> + hash-table.o file-find.o
> +
> ++# Objects compiled from one C source file gcc-ar.c
> ++OBJS-gcc-ar = gcc-ar.o gcc-nm.o gcc-ranlib.o
> ++
> + # This lists all host objects for the front ends.
> + ALL_HOST_FRONTEND_OBJS = $(foreach v,$(CONFIG_LANGUAGES),$($(v)_OBJS))
> +
> + ALL_HOST_BACKEND_OBJS = $(GCC_OBJS) $(OBJS) $(OBJS-libcommon) \
> + $(OBJS-libcommon-target) @TREEBROWSER@ main.o c-family/cppspec.o \
> + $(COLLECT2_OBJS) $(EXTRA_GCC_OBJS) $(GCOV_OBJS) $(GCOV_DUMP_OBJS) \
> +- lto-wrapper.o
> ++ lto-wrapper.o $(OBJS-gcc-ar)
> +
> + # This lists all host object files, whether they are included in this
> + # compilation or not.
> +@@ -2437,6 +2440,8 @@ gengtype-parse.o: $(CONFIG_H)
> + CFLAGS-build/gengtype-parse.o += -DGENERATOR_FILE
> + build/gengtype-parse.o: $(BCONFIG_H)
> +
> ++errors.o : $(CONFIG_H)
> ++
> + gengtype-state.o build/gengtype-state.o: gengtype-state.c $(SYSTEM_H) \
> + gengtype.h errors.h double-int.h version.h $(HASHTAB_H) $(OBSTACK_H) \
> + $(XREGEX_H)
> +--
> +1.8.1.2
> +
>
next prev parent reply other threads:[~2014-07-25 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 10:13 [PATCH V2 0/1] gcc-4.9.inc: fix parallel building failure Hongxu Jia
2014-07-25 10:13 ` [PATCH 1/1] " Hongxu Jia
2014-07-25 15:48 ` Saul Wold [this message]
2014-07-29 1:14 ` Hongxu Jia
-- strict thread matches above, loose matches on Subject: below --
2014-07-29 2:02 [PATCH V3 0/1] " Hongxu Jia
2014-07-29 2:02 ` [PATCH 1/1] " Hongxu Jia
2014-07-24 1:48 [PATCH 0/1] " Hongxu Jia
2014-07-24 1:48 ` [PATCH 1/1] " Hongxu Jia
2014-07-24 2:19 ` 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=53D27C56.9020600@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=hongxu.jia@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.