I'm trying to compile arago-test-image for varsomam33 machine and arago distro with internal toolchain. When bitbake reaches cmem_mod, I get the following error "make[3]: arm-oe-linuxeabi-gcc: Command not found". And arm-oe-linuxeabi-gcc is really not built, real target toolchain is called arm-oe-linux-gnueabi-gcc. After running bitbake -e I see that arm-oe-linuxeabi is the value of TOOLCHAIN_SYS:

# $TOOLCHAIN_SYS
# immediate /home/a-gerasimov/Yocto/meta-arago/meta-arago-distro/conf/distro/include/toolchain-gcc.inc:6
#     "${TARGET_SYS}"
TOOLCHAIN_SYS="arm-oe-linuxeabi"

But TARGET_SYS is set to arm-oe-linux-gnueabi:

# $TARGET_SYS [2 operations]
#   set /home/a-gerasimov/Yocto/poky/meta/conf/bitbake.conf:118
# "${TARGET_ARCH}${TARGET_VENDOR}${@['-' + d.getVar('TARGET_OS', True), ''][d.getVar('TARGET_OS', True) == ('' or 'custom')]}"
#   set /home/a-gerasimov/Yocto/poky/meta/conf/documentation.conf:415
# [doc] "The target system is comprised of TARGET_ARCH,TARGET_VENDOR and TARGET_OS."
# pre-expansion value:
# "${TARGET_ARCH}${TARGET_VENDOR}${@['-' + d.getVar('TARGET_OS', True), ''][d.getVar('TARGET_OS', True) == ('' or 'custom')]}"
TARGET_SYS="arm-oe-linux-gnueabi"

It seems that for some reason when toolchain-gcc.inc is included into distro/arago.conf, TARGET_SYS is set to some weird value, not the one that is set by bitbake.conf. Do you have any ideas about how that is possible and how it can be debugged.
Thank you!
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Reply via email to