Re: Auto-rpath revisited...

[hjl at lucon dot org (H.J. Lu)]

> 
> This is ok when you know what you're doing.  But most users don't know
> g++ links -lstdc++ in, they just expect g++ to do the Right Thing
> (TM).  *You* know what you're doing and what g++ will do, so you'll
> just run gcc ... -R... -lstdc++, or g++ -nostdlib ... -lstdc++, which
> will work.
> 
> I was just worried about C++ programs that rely on libtool libraries:
> libtool would specify -rpath, but it wouldn't know where libstdc++
> was, so that specification would be missing.  But then, if g++ did
> implicitly append libstdc++ to the library path, it should implicitly
> append its runtime directory too.
> 

I'd like to see it as a configuration time option. I don't need it
on my machine. It doesn't do me any good.

BTW, it would be better for g++/c++ to pass -rpath to collect2 since we
can tell g++ where libstdc++ will be installed. If people want to
use

# gcc .... -lstc++

They'd better add -rpath themselves. I can write a patch if necesssary.


-- 
H.J. Lu (hjl@gnu.org)