[OE-core] [PATCH] libtool: Add missing DEPENDS on libtool-cross

Maupin, Chase chase.maupin at ti.com
Thu Oct 4 13:02:28 UTC 2012


> -----Original Message-----
> From: Richard Purdie [mailto:richard.purdie at linuxfoundation.org]
> Sent: Thursday, October 04, 2012 7:58 AM
> To: Maupin, Chase
> Cc: openembedded-core at lists.openembedded.org
> Subject: RE: [OE-core] [PATCH] libtool: Add missing DEPENDS on
> libtool-cross
> 
> On Thu, 2012-10-04 at 12:39 +0000, Maupin, Chase wrote:
> > I was able to reproduce this consistently on my build server
> which has
> > 24 cores running at 3.5 GHz.  I was using:
> >
> > BB_NUMBER_THREADS = "24"
> >
> > And
> >
> > PARALLEL_MAKE = "-j 24"
> >
> > I can try a build reducing the number of threads and see if the
> issue
> > goes away as this might be a difference between our builds.
> Can you
> > tell me what you are using?
> 
> I tested this with 48/48 in master.
> 
> > It seemed like a race condition because after I got the error I
> was
> > able to do a -c cleanall of libtool and kick off the build
> again once
> > libtool-cross was built and it would pass.  Likewise I did:
> >
> > bitbake libtool-cross
> > bitbake libtool
> >
> > and that would work but just
> >
> > bitbake libtool
> >
> > would fail.
> 
> "bitbake libtool" works here quite consistently. I therefore
> don't want
> to add this dependency until we figure out exactly what is racing
> against what or have a better understanding of why this is
> failing.
> Something doesn't seem right as if your premise of a missing
> dependency
> is correct, the above wouldn't work.

Understood.  Let me look closer.  My build setup is an Ubuntu 10.04 system and I'm using an external Arago toolchain as well.  On my setup I can consistently cause this to fail even with a lower number of threads.  So perhaps the issue is not the libtool-cross dependency, but that libtool-cross itself forces something else to be built first.  Thanks for the information on your setup and confirmation that you do not see this issue.

> 
> Cheers,
> 
> Richard
> 
> 



More information about the Openembedded-core mailing list