https://sourceware.org/bugzilla/show_bug.cgi?id=32986
Bug ID: 32986
Summary: installed libtool archives contain references to
build-time paths
Product: binutils
Version: 2.42
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: alexander.gr...@tu-dresden.de
Target Milestone: ---
During compilation `-L $(pwd)/libiberty/pic -liberty` is added to the linker
command.
This then ends up in the installed `libbfd.la`. It likely got there through
`libctf.la` which is also installed and has the same issue.
This is likely related to https://sourceware.org/bugzilla/show_bug.cgi?id=27360
as I think the issue is introduced by
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7d53105d6ed984aec255fa0eacd0405f3c1bb874
but didn't verify that.
To me this looks like a bug as after installation the location of the build
folder should not matter anymore and could even cause issues when it is a
folder later being used for something else, like storing libraries that happen
to be incompatible with the ones expected by the installed binutils.
In our case we have many different versions of software, including binutils,
installed side-by-side and "activate" them setting environment variables like
LD_LIBRARY_PATH. Hence the situation of reused folder and version conflicts is
at least likely.
Is that expected, a bug in libtool or an omission in the configure scripts of
binutils?
--
You are receiving this mail because:
You are on the CC list for the bug.
