From: Ulf Samuelsson <openembedded-core@emagii.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Feedback on building openembedded-core for qemuarm. Excerpts from buildlog
Date: Thu, 08 Dec 2011 00:45:55 +0100 [thread overview]
Message-ID: <4EDFFAB3.6070603@emagii.com> (raw)
In-Reply-To: <20111207225108.GB7003@sakrah.homelinux.org>
On 2011-12-07 23:51, Khem Raj wrote:
> On (04/12/11 11:35), Richard Purdie wrote:
>> On Sun, 2011-12-04 at 12:20 +0100, Henning Heinold wrote:
>>> On Sat, Dec 03, 2011 at 09:03:46PM +0100, Ulf Samuelsson wrote:
>>>> Have made some further tests with the same machine, but now running
>>>> Ubuntu 11.04 x64
>>>>
>>>> bitbake console-image
>>>>
>>>> PARALLEL_TASKS BB_NUMBER_TASKS BUILD TIME
>>>> 2 2
>>>> 1:24:16
>>>> 4 4
>>>> 0:48:22
>>>> 6 6
>>>> 0:45:00
>>>> 24 24
>>>> C++ compiler fails with --sysroot problem
>>>> after ~2200 out of 2400 tasks.
>>>>
>>>>
>>>>
>>>> BR
>>>> Ulf
>>> Hi Ulf,
>>>
>>> can you try the attached patch if it solves the problem?
> Does this really fix the problem.
It apparently fixes the symptoms at least (but I didn't do many tests.
On the other hand, the performance improvement seems minimal
once your past 6-8, even on a hexa core machine.
>> Can someone please explain to me how this would fix the problem?
>>
>> If this were the issue shouldn't it either always work or always fail?
>>
>> I'm worried that even if this does "fix" the problem, there is a deeper
>> issue lurking somewhere :(
> We use --with-local-prefix and then also --with-gxx-include-dir which
> points to /usr/include/c++
>
> Now the documentation says that --with-gxx-include-dir is an absolute
> path but if sysroot gets prepended to it or not I am not clear yet
> if sysroot gets prepended to it then we should be in safe spot
>
>
>> Cheers,
>>
>> Richard
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Best Regards
Ulf Samuelsson
eMagii
prev parent reply other threads:[~2011-12-07 23:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 11:24 Feedback on building openembedded-core for qemuarm. Excerpts from buildlog Ulf Samuelsson
2011-11-26 12:38 ` Eric Bénard
2011-11-26 14:14 ` Ulf Samuelsson
2011-11-27 11:40 ` Richard Purdie
2011-11-27 11:47 ` Eric Bénard
2011-11-28 21:31 ` Ulf Samuelsson
2011-11-29 8:48 ` Eric Bénard
2011-11-29 15:03 ` Richard Purdie
2011-11-29 15:50 ` Koen Kooi
2011-11-29 16:03 ` Richard Purdie
2011-12-01 1:52 ` Khem Raj
2011-12-01 9:26 ` Richard Purdie
2011-11-29 19:36 ` Ulf Samuelsson
2011-11-29 20:06 ` Koen Kooi
2011-11-29 21:12 ` Ulf Samuelsson
2011-12-01 13:16 ` Philip Balister
2011-12-01 15:37 ` Koen Kooi
2011-12-01 16:31 ` Ulf Samuelsson
2011-12-02 9:46 ` Frans Meulenbroeks
2011-12-02 9:49 ` Koen Kooi
2011-12-02 22:36 ` Ulf Samuelsson
2011-11-29 21:18 ` Ulf Samuelsson
2011-11-30 17:30 ` Scott Garman
2011-12-01 14:49 ` Ulf Samuelsson
2011-12-03 20:03 ` Ulf Samuelsson
2011-12-04 11:20 ` Henning Heinold
2011-12-04 11:35 ` Richard Purdie
2011-12-07 22:51 ` Khem Raj
2011-12-07 23:45 ` Ulf Samuelsson [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=4EDFFAB3.6070603@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox