The way of setting up the local linker scripts with gen_usr_ldscript seems incorrect. It's using absolute path rather than relative path. That causes problems during cross compilation - linking phase, as linker reads HOST libraries and fails with: file not recognized: File format not recognized collect2: ld returned 1 exit status Reproducible: Always Steps to Reproduce: I'm using solar's crossdev-wrappers for armv4t arch: grep 4411 /usr/armv4tl-softfloat-linux-gnueabi/usr/lib/* Actual Results: /usr/armv4tl-softfloat-linux-gnueabi/usr/lib/libacl.so: See bug http://bugs.gentoo.org/4411 for more info. /usr/armv4tl-softfloat-linux-gnueabi/usr/lib/libattr.so: See bug http://bugs.gentoo.org/4411 for more info. /usr/armv4tl-softfloat-linux-gnueabi/usr/lib/libblkid.so: See bug http://bugs.gentoo.org/4411 for more info. /usr/armv4tl-softfloat-linux-gnueabi/usr/lib/libbz2.so: See bug http://bugs.gentoo.org/4411 for more info. /usr/armv4tl-softfloat-linux-gnueabi/usr/lib/libcom_err.so: See bug http://bugs.gentoo.org/4411 for more info. everything what's linking against these (and others) libraries fails.
paths in linker scripts are treated relative to the sysroot, not absolute paths
(In reply to comment #1) > paths in linker scripts are treated relative to the sysroot, not absolute paths > So something else must be missing if compiler is picking HOST libraries instead of sysroot's one.
bugzilla is not a support forum. if you have questions, feel free to pursue them in the forums or the gentoo embedded mailing list.
