This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/62290] New: --print-file-name doesn't work for liblto_plugin.so
- From: "amker.cheng at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 28 Aug 2014 07:25:42 +0000
- Subject: [Bug driver/62290] New: --print-file-name doesn't work for liblto_plugin.so
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62290
Bug ID: 62290
Summary: --print-file-name doesn't work for liblto_plugin.so
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: amker.cheng at gmail dot com
At least with revision@214413, gcc configured with below options on x86_64.
$ ../gcc/configure --prefix=....../target/
--enable-languages=c,c++,ada,fortran,java,objc,obj-c++,go
Option --print-file-name=liblto_plugin.so doesn't work for installed GCC.
$ ./gcc -print-file-name=liblto_plugin.so
liblto_plugin.so
The file is installed into
./libexec/gcc/x86_64-unknown-linux-gnu/5.0.0/liblto_plugin.so, but gcc's search
dir for libraries are like below (formatted for easy reading's sake).
./gcc --print-search-dirs
libraries: =
....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/
:....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../../x86_64-unknown-linux-gnu/lib/x86_64-unknown-linux-gnu/5.0.0/:
....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../../x86_64-unknown-linux-gnu/lib/x86_64-linux-gnu/:
....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../../x86_64-unknown-linux-gnu/lib/../lib64/:
....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../x86_64-unknown-linux-gnu/5.0.0/:
....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../x86_64-linux-gnu/:
....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../../lib64/
:/lib/x86_64-unknown-linux-gnu/5.0.0/
:/lib/x86_64-linux-gnu/
:/lib/../lib64/
:/usr/lib/x86_64-unknown-linux-gnu/5.0.0/
:/usr/lib/x86_64-linux-gnu/
:/usr/lib/../lib64/
:....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../../x86_64-unknown-linux-gnu/lib/
:....../target/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/../../../
:/lib/
:/usr/lib/
It happens on arm/aarch64 too.