On Wed, May 05, 2004 at 11:33:21AM -0500, Albert Chin wrote:
> On Wed, May 05, 2004 at 08:14:16AM -0700, Ben Reser wrote:
> > On Wed, May 05, 2004 at 11:02:19AM +0100, Joe Orton wrote:
> > > libtool automatically adds an appropriate RPATH to programs if they are
> > > linked against libtool libraries which will be installed into non-system
> > > directories; -rpath doesn't make any difference at all for that case.
> > >
> > > see e.g. httpd, which doesn't pass -rpath when linking programs yet
> > > works as expected when installed with prefix != /usr.
> >
> > Is this true only after a certain version of libtool? If it's true of a
> > reasonably well deployed set of libtools then maybe we should rip -rpath
> > out of there period.
libtool 1.3 had the logic to add the RPATH automatically, so it's been
there "forever" as far as SVN is concerned.
> >From libtool.info for 1.5:
> `-rpath LIBDIR'
> If OUTPUT-FILE is a library, it will eventually be installed in
> LIBDIR. If OUTPUT-FILE is a program, add LIBDIR to the run-time
> path of the program.
Ah, so it is documented to work for programs somewhere too.
> So, I think it's need for libraries and programs.
Did you read the above statement about libtool automatically adding the
RPATH for $libdir to programs anyway? So why do you think it's needed
for programs?
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 5 21:08:25 2004