From: Denys Dmytriyenko denys@ti.com

libc.so linker script should use relative paths to not clash with host libs. Using absolute paths in libc.so is fine with standalone toolchain or when used inside a rootfs. But when used inside OE SDK for cross-compilation, the absolute path confuses compiler with libs from host environment. In the past, Linaro prebuilt toolchains always had relative paths inside libc.so linker script. Adjust it the same for the Arm prebuilt toolchain.

Signed-off-by: Denys Dmytriyenko denys@ti.com --- .../recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb | 1 + 1 file changed, 1 insertion(+)

diff --git a/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb index 6fb5a4d..a4067d8 100644 --- a/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb +++ b/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb @@ -233,6 +233,7 @@ do_install() { if [ -f ${D}${libdir}/libc.so ];then sed -i -e "s# /${EAT_LIBDIR}/${EAT_TARGET_SYS}# ../../${EAT_LIBDIR}#g" -e "s# /usr/${EAT_LIBDIR}/# /usr/lib/#g" -e "s# /usr/${EAT_LIBDIR}/${EAT_TARGET_SYS}# .#g" -e "s# /${EAT_LIBDIR}/ld-linux# ../../${EAT_LIBDIR}/ld-linux#g" ${D}${libdir}/libc.so sed -i -e "s# /${EAT_LIBDIR}/libc.so.6# /lib/libc.so.6#g" ${D}${libdir}/libc.so + sed -i -e "s# /lib# ../../lib#g" -e "s# /usr/lib# .#g" ${D}${libdir}/libc.so fi

if [ -f ${D}${base_libdir}/libc.so ];then