Re: Broken parallel build of gcc*

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2012-07-20 at 12:41 +0200, Martin Jansa wrote:
> On Fri, Jul 20, 2012 at 12:28:29PM +0200, Enrico Scholz wrote:
> > Hi,
> > 
> > some of the recent changes seem to break the parallel build of the gcc*
> > recipes which are sharing a same source directory:
> > 
> > | $ ./bitbake gcc-cross-initial gcc-cross-intermediate gcc-cross -c cleansstate
> > | $ BB_NUMBER_THREADS=3 ./bitbake gcc-cross-initial gcc-cross-intermediate gcc-cross
> > | ...
> > | NOTE: package gcc-cross-initial-4.7.1.0+git1+d07e24f4ab59f264d68d21838795349faab5dede-r7: task do_unpack: Started
> > | NOTE: package gcc-cross-4.7.1.0+git1+d07e24f4ab59f264d68d21838795349faab5dede-r7: task do_unpack: Started
> > | NOTE: package gcc-cross-initial-4.7.1.0+git1+d07e24f4ab59f264d68d21838795349faab5dede-r7: task do_unpack: Succeeded
> > | ERROR: Error executing a python function in ...recipes-devtools/gcc/gcc-cross_4.7.bb:
> > | OSError: [Errno 39] Directory not empty: '...tmp/work-shared/gcc-4.7.1.0+git1+d07e24f4ab59f264d68d21838795349faab5dede-r7/git/'
> > | NOTE: package gcc-cross-4.7.1.0+git1+d07e24f4ab59f264d68d21838795349faab5dede-r7: task do_unpack: Failed
> > 
> > It seems that the work-shared/ directory is not locked and cleaned when
> > starting the second unpack.
> 
> I can confirm the same
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026174.html

The autobuilder is not seeing this and I'm not seeing it locally either.

This would imply there is some difference in configuration which is
triggering it. rm_work* is a possibility, as could ASSUME_PROVIDED
settings potentially although unlikely.

Encrico: Which DISTRO are you using and do you use rm_work*.bbclass?

Cheers,

Richard