From: Ulf Samuelsson <openembedded-core@emagii.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Reproducible build problem with BB_NUMBER_THREADS=8
Date: Fri, 02 Dec 2011 00:53:22 +0100 [thread overview]
Message-ID: <4ED81372.90200@emagii.com> (raw)
In-Reply-To: <20111201230804.GD9685@sakrah.homelinux.org>
On 2011-12-02 00:08, Khem Raj wrote:
> On (01/12/11 16:59), Ulf Samuelsson wrote:
>> 2011-12-01 15:12, Cliff Brake skrev:
>>> On Thu, Dec 1, 2011 at 7:48 AM, Richard Purdie
>>> <richard.purdie@linuxfoundation.org> wrote:
>>>
>>>> When you restart the build is the problem persistent or does it work the
>>>> second time?
>>> I set BB_NUMBER_THREADS = "2" (was 4 when failing)
>>>
>>> I tried to restart the build and cleanall just the failing package,
>>> and it still failed. I then ran:
>>>
>>> bitbake -c cleanall gcc-cross gcc-cross-initial gcc-cross-intermediate
>>> gcc-runtime
>>>
>>> and after that, everything worked.
>>>
>>>> Does someone have a complete console log for a build that failed with
>>>> this they could share?
>>> I'll restart the build and collect one. So you just want the output
>>> of the console for bitbake?
>>>
>>> Thanks,
>>> Cliff
>>>
>> Here is my buildlog, creating the failure.
>> The C++ compiler cannot find "string", even though it is in
>> "<sysroot>/usr/include/c++"
>>
> This probably might have something to do with-gxx-include settings
> I will see if I can reproduce it here
I have seen the problem on the following machine
Core i7 980X (hexa core) @ 3.33 GHz
12 GB RAM
Ubuntu 11.10 x64
Build on Intel 510 120 GB SSD disk
PARALLEL_MAKE = "24" | "4"
BB_NUMBER_THREADS = "24" | "4".
I have not seen the problem on the following machine
Core i7 920 @ 2.67 GHz
4 GB RAM.
Ubuntu 11.04 x64
WD Black 1TB SATA-II
PARALLEL_MAKE = "4"
BB_NUMBER_THREADS = "4".
The problem comes in two flavours.
The one in the log, but also when building "tiff".
"tiff" bombs with another C++ include.
Someone else had a similar problem, so I cleaned out the build directory,
built tiff, and then console-image, which completed.
I changed my build script to first build tiff, and then console-image
for the next clean build. This time the c++ include problem reappeared.
I guess there is some race condition somewhere.
BR
Ulf Samuelsson
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Best Regards
Ulf Samuelsson
eMagii
next prev parent reply other threads:[~2011-12-02 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 11:03 Reproducible build problem with BB_NUMBER_THREADS=8 Eric Bénard
2011-11-15 14:32 ` Eric Bénard
2011-11-15 20:19 ` Henning Heinold
2011-11-15 20:50 ` Richard Purdie
2011-11-15 21:06 ` Henning Heinold
2011-12-01 12:34 ` Cliff Brake
2011-12-01 12:48 ` Richard Purdie
2011-12-01 14:12 ` Cliff Brake
2011-12-01 15:59 ` Ulf Samuelsson
2011-12-01 17:34 ` Henning Heinold
2011-12-01 21:17 ` Richard Purdie
2011-12-01 21:47 ` Henning Heinold
2011-12-01 23:08 ` Khem Raj
2011-12-01 23:53 ` Ulf Samuelsson [this message]
[not found] <mailman.14454.1321367942.14568.openembedded-core@lists.openembedded.org>
2011-11-15 19:24 ` Daniel Lazzari
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=4ED81372.90200@emagii.com \
--to=openembedded-core@emagii.com \
--cc=openembedded-core@lists.openembedded.org \
--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 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.