You have some setup issues. From config.log your Linaro GCC seems broken: configure:3815: checking whether the C compiler works configure:3837: arm-linux-gnueabihf-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard --sysroot=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/recipe-sysroot -isystem/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0=/usr/src/debug/libtool-cross/2.4.6-r0 -fdebug-prefix-map=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/recipe-sysroot= -isystem/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux -gnueabihf/arm-linux-gnueabihf/include -L/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/lib -Wl,-rpath-link,/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/lib -Wl,-O1 -Wl,--hash-style=gnu conftest.c >&5 /media/disk/users/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/7.2.1/../../../../arm-linux-gnueabihf/bin/ld: cannot find ../../lib/libc.so.6 collect2: error: ld returned 1 exit status [...] configure:3884: error: in `/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/build': configure:3886: error: C compiler cannot create executables
So, since your Linaro GCC cannot cross-compile a simple program, it fails at the first dependency that uses it, which happens to be libtool-cross. Please resolve your setup problems and everything will work w/o any modifications to recipes. Thanks. -- Denys On Wed, Aug 22, 2018 at 03:33:57PM +0000, David Castelow wrote: > Hi, > > I had an issue building the latest TI SDK for Sitara processors > (05_00_00_15), and Kemal from TI suggested I post my findings here for > comment. > > So the build I attempted was for > > $ MACHINE=am335x-evm bitbake arago-base-tisdk-image > > following instructions from > > http > //software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview.html > <http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview.html#id13> > > and using both Linux Mint 17.3 (trusty based) and Ubuntu Xenial (16.04) as > host machines, giving essentially the same error. > > The problem appears in failure to build libtool-cross successfully. > > I have traced this back to something in the bitbake recipes/patches that > modify the libtool configure script: > See http://e2e.ti.com/support/arm/sitara_arm/f/791/p/718479/2660196#2660196 > for the history. > > The build does succeed if I ensure HOST_SYS is defined: > As I said in my last post to that thread, > Compilation/build is successful if I edit > > arago/tisdk/sources/oe-core/meta/classes/nativesdk.bbclass > > -#HOST_SYS = "${HOST_ARCH}${TARGET_VENDOR}-${HOST_OS}" > +HOST_SYS = "${HOST_ARCH}${TARGET_VENDOR}-${HOST_OS}" > > I think this is because there are libtool related .bb files and .patch files > that reference either ${host_alias}-libtool or ${HOST_SYS}-libtool. > > If HOST_SYS is empty, then the executable would be called -libtool, and then > the configure script fails to clean up as it attempts to execute > > rm -libtool > > which won't work as the file name starts with a - (were this to work, it > would need to do the mv/rm of ./${file} rather than just of ${file}). > > I'm not sure if this is the correct solution to the problem, but it suggests > the need to set HOST_SYS as part of the build instructions. > > Can you advise if this is correct? > > [cid:GLOMO2018_e6c86ab3-4fac-42ae-88d7-eab266a26da8.png] tfx > -- > _______________________________________________ > meta-ti mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-ti -- _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
