Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ulf Samuelsson <openembedded-core@emagii.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Feedback on building openembedded-core for qemuarm. Excerpts from buildlog
Date: Sat, 26 Nov 2011 15:14:51 +0100	[thread overview]
Message-ID: <4ED0F45B.8010606@emagii.com> (raw)
In-Reply-To: <4ED0DDBF.9000104@eukrea.com>

On 2011-11-26 13:38, Eric Bénard wrote:
> Hi Ulf,
>
> Le 26/11/2011 12:24, Ulf Samuelsson a écrit :
>> 3. When I ran into this problem, I exited with ctrl-C.
>> This left some recipes in the middle of a fetch ,and the build could not
>> continue.
>> I had to "bitbake -c clean <package>" on all problematic packages to 
>> recover.
>> Seems a little bit fragile to me.
>>
> already met here : you must let bitbake end the other tasks already 
> started to prevent that (so only one control C).
>
>> 4. linux-3.0 recipe in meta-ti does not build (On Ubuntu 11.10 x64).
>> Fails in the fetch stage.
>> I removed the layer, since it was not needed for qemuarm.
>>
> I also met this kind of problem. To prevent that problem, in my bsp 
> overlay, I always add COMPATIBLE_MACHINE = "" to the machine specific 
> recipes.
> What is strange is that meta-ti also have this in its recipes so their 
> linux-3.0 recipe should not be used if you target qemuarm.
>
>> 5. When compiling on a Ubuntu 11.10 x64 host (linux 3.x host)
>> tiff won't build.
>> Did:
>> bitbake console-image"
>> bitbake -c clean tiff
>> bitbake tiff
>> - No luck
>> Reading through the mailing list, I found someone which deleted
>> $TMPDIR and then
>> bitbake tiff
>> bitbake console-image
>> That worked for me as well once, second time, same problem.
>> Problem is that #include <iostream> fails.
>>
>> I noted that "iostream" is built and available in 
>> <sysroot>/usr/include/c++
>> On the host, it is located in /usr/incolude/c++/<version>
>> "tiff" build seems to be OK with Ubuntu 11.04 i686.
>>
> what is your BB_NUMBER_THREADS setting ?
> Here (on 2 different hosts/distro/arch but with an i7 CPU in both 
> cases) if I set it over 4, I often (always with a value of 8) meet 
> problems with c++ includes during build from scratch. 4 seems the 
> magic value which never trigger the problem.

OK, it is higher than that.
Was trying out a Core-i7-980X with 6 cores/12 threads with TMP on a fast 
SSD.
The CPU seems to be running at low frequencies most of the time.


>
> Eric
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


-- 
Best Regards
Ulf Samuelsson
eMagii




  reply	other threads:[~2011-11-26 14:55 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 [this message]
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

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=4ED0F45B.8010606@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