From: Henning Heinold <heinold@inf.fu-berlin.de>
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: Tue, 15 Nov 2011 22:06:16 +0100 [thread overview]
Message-ID: <20111115210616.GD3773@mail.adw-basketball.de> (raw)
In-Reply-To: <1321390249.26881.227.camel@ted>
On Tue, Nov 15, 2011 at 08:50:49PM +0000, Richard Purdie wrote:
> On Tue, 2011-11-15 at 21:19 +0100, Henning Heinold wrote:
> > On Tue, Nov 15, 2011 at 12:03:45PM +0100, Eric Bénard wrote:
> > > Hi,
> > >
> > > I often meet a problem related to C++ headers which are not found
> > > (despite existing)n often when bitbake starts compiling mysql &
> > > directfb.
> > > I tested on 2 build hosts (both with Core i7, one i686 ubuntu, one
> > > x64_64 Fedora) and manage to reproduce the problem easily with
> > > BB_NUMBER_THREADS=8 in both cases.
> > >
> > > The configuration is quite simple :
> > > angstrom setup script + beagleboard machine + bitbake qt4e-demo-image
> > > with
> > > PARALLEL_MAKE = "-j6"
> > > BB_NUMBER_THREADS = "8"
> >
> > Hi Eric,
> >
> > I found another problem with the crosscompiler setup and c++,
> > while compile llvm with cmake.
> >
> > In recipes-devtools/gcc/gcc-configure-cross.inc we set
> >
> > EXTRA_OECONF_PATHS = "--with-local-prefix=${STAGING_DIR_TARGET}${target_exec_prefix} \
> > --with-gxx-include-dir=${target_includedir}/c++ \
> > --with-sysroot=${STAGING_DIR_TARGET} \
> > --with-build-sysroot=${STAGING_DIR_TARGET}"
> >
> >
> > which results in a headersearch path for c++
> >
> > .../usr/usr/include/c++
> >
> > unfornatly I do not have the time to test it some more. But this little patch plus INC bumping
> > sovled it for my setup:
> >
> > -EXTRA_OECONF_PATHS = "--with-local-prefix=${STAGING_DIR_TARGET}${target_exec_prefix} \
> > +EXTRA_OECONF_PATHS = "--with-local-prefix=${STAGING_DIR_TARGET} \
>
> How does that cause something which sometimes works and sometimes does
> not? Either it would work or wouldn't if this were the problem but not
> "sometimes"?
>
> Cheers,
>
> Richard
Yes,
I hijacked the thread. Sorry.
Bye Henning
next prev parent reply other threads:[~2011-11-15 21:12 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 [this message]
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
[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=20111115210616.GD3773@mail.adw-basketball.de \
--to=heinold@inf.fu-berlin.de \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox