/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/autom4te: build/tmp-angstrom_2010_x-eglibc/sysroot: bad interpreter:
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
Quoted 10 lines · Jonathan Cameron
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_sysrootended 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.1218for further information)
Quoted 4 lines
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...
It wasn't. Now getting the same error, on libtool native, but now with an apparently valid path..
Quoted 6 lines
Anyone have any other thoughts on what might have broken this?
Thanks,
Jonathan
Quoted 11 lines · Jonathan Cameron
Quoted 10 lines · Jonathan Cameron
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_sysrootended 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.1218for further information)
Quoted 7 lines
Quoted 4 lines
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...
It wasn't. Now getting the same error, on libtool native, but now with an apparently valid path..
Quoted 2 lines
Anyone have any other thoughts on what might have broken this?
Missed wiping the caches, now looks like it might be working...