This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Path to libstdc++
On Tuesday 26 March 2002 16:33, Alexandre Oliva wrote:
> On Mar 25, 2002, Allan Sandfeld Jensen <snowwolf@one2one-networks.com>
wrote:
> > it used to also put a -Wl,-rpath,$LIBSTDC++-PATH or
> > equivalent, but this has disappeared recently in current-cvs.
>
> Not true. GCC never ever did this, on any platform, and my attempts
> to get it to do so have always been overruled.
>
> What I do myself is to tweak the gcc linker specs file such that it
> adds the flag for me. Works fine except on platforms that require
> library search paths to be passed as a single colon-separated
> argument. And it also modifies the behavior of the linker, because
> then it never gets to see LD_RUN_PATH or equivalent.
What about letting g++ pass both -rpath $libpath and -rpath $LD_RUN_PATH? That
way we keep linker behavior.
For hpux I've found a small hack. Link applications with -Wl,+b:
+b is hpux-ld -rpath argument and the single colon is magic for use -L$PATH as
-rpath, and g++ always specifies the "correct path"(g++ lib-installpath) for
-L (link-time lib-searchpath).
But I still dont see why not always to specify the same path for -rpath. It
cant give any more problems at run-time than giving it to -L might give at
link-time.