This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
print-file-name
- To: gcc-bugs at gcc dot gnu dot org
- Subject: print-file-name
- From: Daniel Wagner <wagi at gmx dot ch>
- Date: Mon, 12 Feb 2001 23:50:39 +0100
[note: I'm not on the list, so please cc me]
Hello,
I'm bit confused about the print-file-name options. I thought that
should print the whole path to a library, but I only honors libraries
which are located in /lib. I tested it with setting LD_LIBRARY_PATH and
ld.so.conf both with the same result. For example:
wagi@aragorn:/lib$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.2/specs
gcc version 2.95.2 20000220 (Debian GNU/Linux)
wagi@aragorn:~$ ls /usr/local/lib -1
[...]
liboskit_amm.a
liboskit_bootp.a
liboskit_c.a
liboskit_clientos.a
liboskit_com.a
[...]
libtilurcomponents.so
libtilurcomponents.so.0
libtilurcomponents.so.0.0.0
oskit
python1.5
site-python
site_perl
texmf
xemacs
wagi@aragorn:~$export LD_LIBRARY_PATH=/usr/local/lib
wagi@aragorn:~$gcc -print-file-name=oskit
oskit
The Right Thing(c) would be: /usr/local/lib/oskit
When I do a simlink from /usr/local/lib/oskit to /lib
then this happends:
wagi@aragorn:/lib$ sudo ln -s /usr/local/lib/oskit/ .
wagi@aragorn:/lib$ gcc -print-file-name=oskit
/lib/oskit
Do I miss something here? Or is this really a bug?
thanks,
wagi
--
Daniel Wagner
email: wagi@gmx.ch
GnuPG: 1024D/DCDE890A (public key available on any keyserver)