Summary: | sys-fs/e2fsprogs-1.40.5 fails to compile due to local linker scripts | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andriy Baranskyy <andriy155> |
Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andrei.ivanov, kanaka |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andriy Baranskyy
2008-01-28 08:19:36 UTC
the same here *** Bug 207856 has been marked as a duplicate of this bug. *** The new way of setting up the local linker scripts doesn't work with --sysroot style cross-compilers: echo "GROUP ( /usr/$(get_libdir)/libcom_err.a )" > lib/libcom_err.a echo "GROUP ( /usr/$(get_libdir)/libcom_err.so )" > lib/libcom_err.so echo "GROUP ( /usr/$(get_libdir)/libss.a )" > lib/libss.a echo "GROUP ( /usr/$(get_libdir)/libss.so )" > lib/libss.so The problem here is that toolchain programs with --sysroot support will normally resolve linker script GROUP values to be relative to the value of sysroot. However, they only do this if the file containing the linker script is within the sysroot. Otherwise it uses an absolute path which ends up picking up system libraries when cross-compiling. I.e. this happens: CC prof_err.c LD e2fsck /usr/libexec/gcc/mips64el-gentoo-linux-gnu/ld: cannot find /usr/lib32/libcom_err.so collect2: ld returned 1 exit status file a new bug |