From: "Eric Bénard" <eric@eukrea.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: ulf@emagii.com,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-4.6: Let G++ relocate gxx-include-dir when using --sysroot option
Date: Wed, 21 Dec 2011 15:23:45 +0100 [thread overview]
Message-ID: <4EF1EBF1.4090509@eukrea.com> (raw)
In-Reply-To: <CAMKF1soiqXt3dcJea5o=54bTaJNGUxRDHBoHe6TWa-hEx=AgHw@mail.gmail.com>
Hi Khem,
Le 20/12/2011 20:59, Khem Raj a écrit :
> On Mon, Dec 19, 2011 at 10:36 PM, Eric Bénard<eric@eukrea.com> wrote:
>> Hi, Khem,
>>
>> Le 14/12/2011 19:38, Khem Raj a écrit :
>>
>>> On Wed, Dec 14, 2011 at 10:08 AM, Ulf Samuelsson
>>> <openembedded-core@emagii.com> wrote:
>>>>>
>>>>>
>>>>>
>>>> Not familiar with gcc internals, but just want to reiterate the
>>>> point that the problem occured (the one I saw) only when I had
>>>> BB_NUMBER_THREADS at a high value, so WHEN things are done seems to
>>>> be important.
>>>
>>>
>> Seems more complicated than this. A customeer reproduced it with
>> BB_THREAD=2 and PARALLEL=j3 ... (I never reproduced in with BB_THREAD<
>> 5)
>>
>
> Can you see when gcc-runtime was finished building and staging w.r.t to the
> failing app
>
rm_work on gcc-runtime was done far before do_configure on the failing app
(mysql in the present case).
Eric
prev parent reply other threads:[~2011-12-21 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 8:28 [PATCH] gcc-4.6: Let G++ relocate gxx-include-dir when using --sysroot option Khem Raj
2011-12-14 10:02 ` Richard Purdie
2011-12-14 15:49 ` Khem Raj
2011-12-15 12:16 ` Richard Purdie
2011-12-16 21:24 ` Khem Raj
2011-12-20 9:07 ` Martin Jansa
2011-12-20 9:37 ` Martin Jansa
2011-12-20 16:15 ` Martin Jansa
2011-12-20 17:45 ` Khem Raj
2011-12-14 18:08 ` Ulf Samuelsson
2011-12-14 18:38 ` Khem Raj
2011-12-20 6:36 ` Eric Bénard
2011-12-20 19:59 ` Khem Raj
2011-12-21 14:23 ` Eric Bénard [this message]
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=4EF1EBF1.4090509@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ulf@emagii.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox