From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Pb compilation with BB_NUMBER_THREADS != 1
Date: Mon, 04 Nov 2013 12:52:57 -0700 [thread overview]
Message-ID: <5277FB19.80807@mlbassoc.com> (raw)
In-Reply-To: <F48900D76F0D8349918584FEEFEB4BCA06003FE2@SEXCHANGE0100.lpg.priv>
On 2013-11-04 09:44, MONDON Daniel wrote:
> I'm on a virtual Ubuntu 12.04 server, 16 cores, 8Go RAM free frequency (max = 163840MHz)
>
> With BB_NUMBER_THREADS = '1', the entire project is successfully build in 12h30.
>
> With BB_NUMBER_THREADS = '4' (same result with 12)
>
> | LD_LIBRARY_PATH=/home/xxxxxxxxxxbuild/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/perl-native-5.14.2-r0/perl-5.14.2:/home/xxxxxxxxxxbuild/tmp-angstrom_v2012_05-eglib
> c/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib:/home/xxxxxxxxxxbuild/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/bin/../lib/pseudo/lib64 ./perl -f -Ilib pod/buildtoc --
> build-toc -q
> |
> | Making x2p stuff
> | make[1]: Entering directory `/home/xxxxxxxxxxbuild/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/perl-native-5.14.2-r0/perl-5.14.2/x2p'
> |
> | make[1]: Leaving directory `/home/xxxxxxxxxxbuild/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/perl-native-5.14.2-r0/perl-5.14.2/x2p'
> | pod/buildtoc: no pods at pod/buildtoc line 305.
> | make: *** [pod/perltoc.pod] Error 255
> | ERROR: oe_runmake failed
> NOTE: package perl-native-5.14.2-r0: task do_compile: Failed
> NOTE: package perl-5.14.2-r6: task do_fetch: Started
> NOTE: package perl-5.14.2-r6: task do_fetch: Succeeded
> ERROR: Task 1239 (/home/xxxxxxxxxxsources/openembedded-core/meta/recipes-devtools/perl/perl-native_5.14.2.bb, do_compile) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 4055 tasks of which 4053 didn't need to be rerun and 1 failed.
>
> Summary: 1 task failed:
> /home/xxxxxxxxxxsources/openembedded-core/meta/recipes-devtools/perl/perl-native_5.14.2.bb, do_compile
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> Known problem ?
> Any solution ?
More details are probably needed to be able to help much.
Since this is a virtual server, have you tried reducing the number of cores
(not BB threads)? I routinely use this on real Ubuntu-12.04/x86_84 with an
Core2-duo (2x2 cores) with BB_NUMBER_THREADS=4 with no problems.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-11-04 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 16:44 Pb compilation with BB_NUMBER_THREADS != 1 MONDON Daniel
2013-11-04 19:52 ` Gary Thomas [this message]
2013-11-05 8:33 ` MONDON Daniel
2013-11-05 9:28 ` MONDON Daniel
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=5277FB19.80807@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@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 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.