From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: coreutils-native race
Date: Fri, 14 Aug 2009 16:44:16 +0100 [thread overview]
Message-ID: <1250264656.12282.1273.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <200908141710.43549.u.luckas@road.de>
On Fri, 2009-08-14 at 17:10 +0200, Uli Luckas wrote:
> What happens (once in a while) is that some build process uses commands from
> coreutils-native while coreutils-native is being staged.
> Let's say the command is 'rm' - so coreutils-native stages 'rm' while another
> build process trys to delete some file. This leads to "rm: text file busy"
> because rm is still open for writing.
>
> Has anyone seen this? And is there a known fix or workaround?
I guess the fix would be to make coreutils-native install its binaries
atomically (i.e. install them to ${STAGING_BINDIR}/rm.new and then mv
them into place) rather than installing them directly into their final
location. Alternatively you could probably patch it to just not install
things like rm at all: if your host system doesn't have a functioning
"rm" then you're probably hosed anyway.
p.
next prev parent reply other threads:[~2009-08-14 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 15:10 coreutils-native race Uli Luckas
2009-08-14 15:44 ` Phil Blundell [this message]
2009-08-17 14:30 ` [PATCH] " Uli Luckas
2009-09-25 9:54 ` Leon Woestenberg
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=1250264656.12282.1273.camel@mill.internal.reciva.com \
--to=pb@reciva.com \
--cc=openembedded-devel@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 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.