From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Broken parallel build of gcc*
Date: Fri, 20 Jul 2012 12:28:29 +0200 [thread overview]
Message-ID: <lyk3xy7mlu.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
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.
Enrico
next reply other threads:[~2012-07-20 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 10:28 Enrico Scholz [this message]
2012-07-20 10:41 ` Broken parallel build of gcc* Martin Jansa
2012-07-20 11:06 ` Richard Purdie
2012-07-20 11:53 ` Enrico Scholz
2012-07-20 12:04 ` Richard Purdie
2012-07-20 12:15 ` Enrico Scholz
2012-07-20 12:28 ` Richard Purdie
2012-07-20 12:30 ` Martin Jansa
2012-07-20 12:44 ` Enrico Scholz
2012-07-21 14:39 ` Enrico Scholz
2012-07-22 8:43 ` Richard Purdie
2012-07-22 9:43 ` Enrico Scholz
2012-07-22 10:35 ` Richard Purdie
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=lyk3xy7mlu.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.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