From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: race between aclocal and unstaging of .m4 files
Date: Mon, 29 Oct 2012 15:45:19 +0000 [thread overview]
Message-ID: <1351525519.2828.13.camel@ted> (raw)
In-Reply-To: <1351521750.13864.12.camel@phil-desktop>
On Mon, 2012-10-29 at 14:42 +0000, Phil Blundell wrote:
> If do_configure() from one recipe runs in parallel with
> sysroot_cleansstate() from another then aclocal may fail because it
> doesn't react very well to .m4 files disappearing underneath it. This
> manifests as slightly obscure failures such as:
>
> | aclocal: error: aclocal: file '.../tmp-eglibc/sysroots/x86_64-linux/share/aclocal/alsa.m4' does not exist
>
> where the .m4 file in question is not one that the recipe being built
> would actually want to use. (The alsa.m4 error above actually occurred
> during a build of attr.)
>
> There seem to be two obvious ways of fixing this:
>
> a) Add more locking so that these things can't happen in parallel
>
> b) Patch aclocal to make this situation non-fatal
>
> My inclination would be to do (b) since it's less intrusive. Any
> objections or better suggestions?
Does current master not resolve this by creating a copy of the aclocal
directory using hardlinks and using that?
We've gone around in circles on this but I think its fixed once and for
all now.
Cheers,
Richard
prev parent reply other threads:[~2012-10-29 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 14:42 race between aclocal and unstaging of .m4 files Phil Blundell
2012-10-29 15:45 ` Richard Purdie [this message]
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=1351525519.2828.13.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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.