From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: The coreutils-native race...
Date: Sun, 25 Apr 2010 21:28:13 +0200 [thread overview]
Message-ID: <hr254d$kkn$1@dough.gmane.org> (raw)
In-Reply-To: <1272217739.3865.546.camel@trini-m4400>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 25-04-10 19:48, Tom Rini wrote:
> Hey all. I thought I would try and explain what Chris has been up to
> with at least some of the base.bbclass changes (the ones related to
> md5sum and cp).
>
> Right now, with a big enough BB_NUM_THREADS we can get into a race where
> coreutils-native is installing programs and elsewhere we are in a
> do_fetch and either trying to use 'cp' or 'md5sum', and blam, we try and
> invoke the program while it's being installed (and see things like
> sh: /path/to/staging/i686-linux/usr/bin/cp: Textfile is busy).
>
> There's a few ways out of this:
> 1) Don't rely on 'cp' and 'md5sum' anymore but use python for it.
> 2) Make an oe_cp and oe_md5sum to go with oe_sha256sum
> 3) IIRC, the big part of coreutils-native was a fully functional,
> always, 'install'. We could just copy the install we build or provide
> an install wrapper (oe_install) or so
> 4) ???
Even thought I loathe python, option 1 sounds like a nice way to go
since it doesn't involve butchering recipes.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL1JfMMkyGM64RGpERAncaAJ41plrV7jSmlXFUa5AY1VXzIulpggCfeWsr
+7/jI/XS67azRPdGlJJLmYo=
=vq5J
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-25 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 17:48 The coreutils-native race Tom Rini
2010-04-25 18:51 ` Phil Blundell
2010-04-25 19:28 ` Koen Kooi [this message]
2010-04-25 19:57 ` Tom Rini
2010-04-26 6:30 ` Koen Kooi
2010-04-26 14:59 ` Chris Larson
2010-04-25 20:42 ` Roman I Khimov
2010-04-25 21:12 ` Tom Rini
2010-04-25 21:16 ` Yuri Bushmelev
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='hr254d$kkn$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox