ld doesn't honor sysroot prefix for ldscripts - track upstream bug
Bug #625320 reported by
Peter Pearse
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
binutils |
Fix Released
|
Medium
|
|||
binutils (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: binutils
This bug opened to track http://
Changed in binutils (Ubuntu): | |
status: | New → In Progress |
Changed in binutils: | |
status: | Unknown → Confirmed |
Changed in binutils: | |
importance: | Unknown → Medium |
Changed in binutils: | |
status: | Confirmed → In Progress |
Changed in binutils: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
When ld is configured with a sysroot prefix and test is executed:
echo "Testing with absolute linker script (systems libz)..." /libfoo- script. so" softfloat- linux-gnueabi- gcc test.c -o test libfoo-script.so
echo "GROUP ( /lib/libz.so )" > "${PWD}
armv4tl-
the linking process terminates with
Testing with absolute linker script (systems libz)...
/lib/libz.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
because the Host's library is linked in. For cross-compilation the desired
behaviour is different. Here, the lib specified in the linker script should be
searched in the sysroot first! Patch will be attached.