Re: Using -Bsymbolic with libtool

[Robert Boehne]

Ganesan Rajagopal wrote:
> 
> >>>>> "Robert" == Robert Boehne <address@hidden> writes:
> 
> > I think you can get the exact same result by using the
> > -Wl,-Bsymbolic flag.  It will be recognized by Libtool,
> > and passed to the linker.  -Xlinker is a gcc equivalent
> > to -Wl, so if I recall correctly, that would only work
> > when using GCC.  If using -Wl,-Bsymbolic does the trick
> > even whey you're using libtool, then there is no need
> > to alter Libtool.
> 
> I know about the -Wl flag. I some how got the idea that -Xlinker is a
> libtool flag which will use the appropriate option to pass it to the linker,
> I don't where I got that idea - it's obviously a gcc specific option.
> 
> >   As for $ORIGIN, I think the same applies, just add
> > -R $ORIGIN to your links.
> 
> > `-R LIBDIR'
> >      If OUTPUT-FILE is a program, add LIBDIR to its run-time path.  If
> >      OUTPUT-FILE is a library, add -RLIBDIR to its DEPENDENCY_LIBS, so
> >      that, whenever the library is linked into a program, LIBDIR will
> >      be added to its run-time path.
> 
> Unfortunately that's not very portable. Tru64 needs -rpath as the flag, not
> -R.
> 
> Ganesan
> 

In this case you'd be passing -R LIBDIR to libtool, not the linker or
compiler, and libtool would translate it into the linker-specific
option,
when one is available.  (The snippet above is from the Libtool
documenation.)
This should be exactly what you're looking for,
and libtool already supports it! :)

Robert

-- 
Robert Boehne             Software Engineer
Ricardo Software   Chicago Technical Center
TEL: (630)789-0003 x. 238
FAX: (630)789-0127
email:  address@hidden