From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Bai, Haiqing" <Haiqing.Bai@windriver.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gmp: depends on flex-native to fix parallel building issue
Date: Tue, 12 Dec 2017 09:22:32 +0000 [thread overview]
Message-ID: <1513070552.19417.153.camel@linuxfoundation.org> (raw)
In-Reply-To: <C2A454FDE6C23F41BD5011E2458C46C9CEF081F1@ALA-MBD.corp.ad.wrs.com>
Let me make this simpler. Which release of the project did you see this
issue with?
I believe this issue would only occur with morty and early, pyro, rocko
and master are not affected.
Cheers,
Richard
On Tue, 2017-12-12 at 07:13 +0000, Bai, Haiqing wrote:
> Comments below. thanks
>
> -----Original Message-----
> From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> Sent: 2017年12月11日 6:48
> To: Bai, Haiqing; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] gmp: depends on flex-native to fix
> parallel building issue
>
> On Wed, 2017-11-29 at 14:54 +0800, Haiqing Bai wrote:
> >
> > fix below parallel building issue:
> > configure:27365: result: flex
> > configure:27403: flex conftest.l
> > .../sysroots/x86_64-linux/usr/bin/flex.real: No such file or
> > directory
> > configure:27407: $? = 127
> > configure:27409: checking lex output file root
> > configure:27420: error: cannot find output from flex; giving up
> >
> > Signed-off-by: Haiqing Bai <Haiqing.Bai@windriver.com>
> > ---
> > meta/recipes-support/gmp/gmp.inc | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-support/gmp/gmp.inc b/meta/recipes-
> > support/gmp/gmp.inc index abac8cf..1b35eaa 100644
> > --- a/meta/recipes-support/gmp/gmp.inc
> > +++ b/meta/recipes-support/gmp/gmp.inc
> > @@ -10,3 +10,5 @@ PACKAGECONFIG[readline] = "--with-readline=yes,
> > --with-readline=no,readline"
> >
> > ARM_INSTRUCTION_SET_armv4 = "arm"
> > ARM_INSTRUCTION_SET_armv5 = "arm"
> > +
> > +DEPENDS = "flex-native"
> With recipe specific sysroots this should now be deterministic. The
> log above suggests you were not using recipe specific sysroots? This
> would therefore only be applicable to morty and earlier?
> [This issue is founded on x86-64 building, but it does not mean it
> is only related with x86. Actually this is caused by the defect of
> the traditional probe mechanism of 'configure', the package
> configure
> script try to probe whether has package 'flex' , then some optional
> actions will be done by it. In this issue, when this probe
> happens, /usr/bin/flex exists but '/usr/bin/flex.real' has not
> created for the
> parallel building, then configure reports the error and exits from
> building. Since there are no atomic guarantee for the package
> output during parallel building, so here add this depends]
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2017-12-12 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 6:54 [PATCH] gmp: depends on flex-native to fix parallel building issue Haiqing Bai
2017-12-10 22:48 ` Richard Purdie
2017-12-12 7:13 ` Bai, Haiqing
2017-12-12 9:22 ` Richard Purdie [this message]
2017-12-13 7:24 ` Bai, Haiqing
2018-01-03 21:35 ` Randy MacLeod
2018-01-03 21:51 ` Richard Purdie
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=1513070552.19417.153.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Haiqing.Bai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox