From: Peter Seebach <peter.seebach@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: heads up, pseudo-1.4.3 has one buggy use case...
Date: Tue, 12 Feb 2013 15:53:01 -0600 [thread overview]
Message-ID: <20130212155301.75a8e76d@e6410-2> (raw)
link() calls inside a chroot tend to fail. Conveniently, nearly
everyone uses linkat() so this doesn't affect most builds, but we found
a test case where it was really easy to trigger.
Symptom: RPM installs saying somehing like:
pseudo: Fatal: Tried to stat
'/home/seebs/pseudo/r/home/seebs/pseudo/r/usr/share/terminfo/a/adm1178;511ab539'
after linking it, but failed: No such file or directory.
Note the double presence of the chroot path. Patch is done in the
pseudo tree, I'll try to get a 1.4.4 out today. Sorry for any
inconvenience!
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
reply other threads:[~2013-02-12 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130212155301.75a8e76d@e6410-2 \
--to=peter.seebach@windriver.com \
--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