From: Jonathan Cameron <jic23@cam.ac.uk>
To: openembedded-core@lists.openembedded.org
Subject: /build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/autom4te: build/tmp-angstrom_2010_x-eglibc/sysroot: bad interpreter:
Date: Mon, 27 Jun 2011 17:34:46 +0100 [thread overview]
Message-ID: <4E08B126.9090106@cam.ac.uk> (raw)
Building a couple of different things today gave me an issue that boils down to the subject line.
Latest issue was eglibc where do_populate_sysroot ended with.
+ autoconf
/home/jic23/src/beagle/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/autoconf: /home/jic23/src/beagle/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/autom4te: /home/jic23/src/beagle/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroot: bad interpreter: No such file or directory
/home/jic23/src/beagle/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/autoconf: line 501: /home/jic23/src/beagle/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/autom4te: Success
ERROR: Function 'do_siteconfig_gencache' failed (see /home/jic23/src/beagle/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/eglibc-2.12-r15/temp/log.do_populate_sysroot.1218 for further information)
Which is true. The directory is sysroots not systroot.
I guess it could be a dead tmp issue so will try rebuilding from scratch overnight...
Anyone have any other thoughts on what might have broken this?
Thanks,
Jonathan
next reply other threads:[~2011-06-27 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 16:34 Jonathan Cameron [this message]
2011-06-27 16:47 ` /build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/autom4te: build/tmp-angstrom_2010_x-eglibc/sysroot: bad interpreter: Jonathan Cameron
2011-06-28 8:44 ` Jonathan Cameron
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=4E08B126.9090106@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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 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.