From: Graham Gower <graham.gower@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: nspr-4.7.1: race condition causing occasional build failure
Date: Wed, 20 Oct 2010 10:06:26 +1030 [thread overview]
Message-ID: <4CBE2B7A.4040601@gmail.com> (raw)
The failure looks like this:
make[3]: Entering directory `/mnt/oe/tmp/work/mipsel-oe-linux/nspr-4.7.1-r1/nspr-4.7.1/mozilla/nsprpub/pr/include/md'
../../../config/./nsinstall -R -m 444 ./_aix32.cfg ./_aix64.cfg ./_beos.cfg ./_bsdi.cfg ./_darwin.cfg ./_dgux.cfg ./_freebsd.cfg ./_hpux32.cfg ./_hpux64.cfg ./_irix32.cfg ./_irix64.cfg ./_linux.cfg ./_ncr.cfg ./_nec.cfg ./_netbsd.cfg ./_nextstep.cfg ./_nto.cfg ./_openbsd.cfg ./_openvms.cfg ./_os2.cfg ./_osf1.cfg ./_qnx.cfg ./_reliantunix.cfg ./_riscos.cfg ./_scoos.cfg ./_solaris.cfg ./_sony.cfg ./_sunos4.cfg ./_unixware.cfg ./_unixware7.cfg ./_win16.cfg ./_win95.cfg ./_winnt.cfg ../../../dist/include/nspr/md
../../../config/./nsinstall: ../../../config/./nsinstall: cannot execute binary file
make[3]: *** [export] Error 126
do_compile_prepend() contains the following line:
cp ${STAGING_BINDIR_NATIVE}/${P}/nsinstall config/nsinstall
Which copies the nsinstall program built by nspr-tools-native. However,
in the case of the failure, nspr chooses to build a version of nsinstall
for the target.
I'm having trouble reproducing this, but I can see that I am not alone
in experiencing this bug.
http://tinderbox.openembedded.net/packages/764121/
Any help with determining what causes this race would be appreciated. It has
the follow on effect of causing various other packages to fail in difficult
to diagnose ways.
-Graham
next reply other threads:[~2010-10-19 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 23:36 Graham Gower [this message]
2010-10-20 5:43 ` nspr-4.7.1: race condition causing occasional build failure Graham Gower
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=4CBE2B7A.4040601@gmail.com \
--to=graham.gower@gmail.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.