From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Jacob Kroon <jacob.kroon@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] bison: fix the parallel build
Date: Thu, 14 May 2020 15:59:34 +0800 [thread overview]
Message-ID: <5EBCFA66.5010902@windriver.com> (raw)
In-Reply-To: <17e2ea0e-6588-355a-9f5a-b570a0e4cf87@gmail.com>
Hi Jacob,
On 05/14/20 15:55, Jacob Kroon wrote:
> Hi Mingli,
>
> On 5/14/20 9:39 AM, Yu, Mingli wrote:
>> From: Mingli Yu <mingli.yu@windriver.com>
>>
>> Explicitly make the BUILT_SOURCES which
>> are the generated headers such as stdio.h,
>> fcntl.h and etc to be the dependencies of
>> the gl_LIBOBJS such as libbison_a-sprintf.o,
>> libbison_a-printf.o and etc to guarantee the
>> BUILT_SOURCES is generated before begin to
>> compile EXTRA_lib_libbison_a_SOURCES such as
>> fprintf.c in parallel builid, otherwise there
>> may come below error:
>> | muscle-tab.c:(.text+0x77a): undefined reference to `rpl_sprintf'
>>
>> It does the same for src_bison_OBJECTS and
>> lib_libbison_a_OBJECTS to make sure BUILT_SOURCES
>> generated before begin to compile src_bison_SOURCES
>> which contains AnnotationList.c and etc.
>>
>> BTW, the MOSTLYCLEANFILES also contains the
>> generated header needs to be created early
>> in the build process, so add it also in to
>> avoid below error:
>> | ./lib/uniwidth/width.c:21:10: fatal error: uniwidth.h: No such
>> file or directory
>>
>> [YOCTO #13825]
>>
>> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
>> ---
>> .../0001-bison-fix-the-parallel-build.patch | 63 +++++++++++++++++++
>> meta/recipes-devtools/bison/bison_3.5.4.bb | 1 +
>> 2 files changed, 64 insertions(+)
>> create mode 100644
>> meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
>>
>> diff --git
>> a/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
>> b/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
>>
>> new file mode 100644
>> index 0000000000..c3be91a109
>> --- /dev/null
>> +++
>> b/meta/recipes-devtools/bison/bison/0001-bison-fix-the-parallel-build.patch
>>
>> @@ -0,0 +1,63 @@
>> +From e0dbcee6e25b3c0cb11a627bbfe3af45ef67ec30 Mon Sep 17 00:00:00 2001
>> +From: Mingli Yu <mingli.yu@windriver.com>
>> +Date: Thu, 14 May 2020 15:23:16 +0800
>> +Subject: [PATCH] bison: fix the parallel build
>> +
>> +Explicitly make the BUILT_SOURCES which
>> +are the generated headers such as stdio.h,
>> +fcntl.h and etc to be the dependencies of
>> +the gl_LIBOBJS such as libbison_a-sprintf.o,
>> +libbison_a-printf.o and etc to guarantee the
>> +BUILT_SOURCES is generated before begin to
>> +compile EXTRA_lib_libbison_a_SOURCES such as
>> +fprintf.c in parallel builid, otherwise there
>> +may come below error:
>> + | muscle-tab.c:(.text+0x77a): undefined reference to `rpl_sprintf'
>> +
>> +It does the same for src_bison_OBJECTS and
>> +lib_libbison_a_OBJECTS to make sure BUILT_SOURCES
>> +generated before begin to compile src_bison_SOURCES
>> +which contains AnnotationList.c and etc.
>> +
>> +BTW, the MOSTLYCLEANFILES also contains the
>> +generated header needs to be created early
>> +in the build process, so add it also in to
>> +avoid below error:
>> + | ./lib/uniwidth/width.c:21:10: fatal error: uniwidth.h: No such
>> file or directory
>> +
>> +Upstream-Status: Submitted [bison-patches@gnu.org maillist]
>> +
>
> I can't find the patch email in the bison-patches mailing list archive,
> do you have a link url ?
Good catch, that's why I didn't paste the link in the Submitted part.
BTW, I also cannot find at
https://lists.gnu.org/archive/html/bison-patches/2020-05/threads.html
though I indeed sent to bison-patches@gnu.org.
Thanks,
Mingli
>
> /Jacob
>
next prev parent reply other threads:[~2020-05-14 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 7:39 [PATCH] bison: fix the parallel build Yu, Mingli
2020-05-14 7:55 ` [OE-core] " Jacob Kroon
2020-05-14 7:59 ` Yu, Mingli [this message]
2020-05-15 1:55 ` Yu, Mingli
2020-05-15 5:53 ` Jacob Kroon
2020-06-01 22:56 ` Andre McCurdy
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=5EBCFA66.5010902@windriver.com \
--to=mingli.yu@windriver.com \
--cc=jacob.kroon@gmail.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.