[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn 0.9 rc2 tarball

From: Blair Zajac <blair_at_orcaware.com>
Date: 2002-02-17 00:25:10 CET

Joe Orton wrote:
>
> On Sat, Feb 16, 2002 at 01:23:52PM -0800, Blair Zajac wrote:
> > Joe Orton wrote:
> > > If you don't mind doing that, you might be able to pass LDLFAGS="-R
> > > path" on your env line below - I think that should work. Alternatively
> > > set LD_LIBRARY_PATH, or configure your system to add the OpenSSL
> > > directory to the runtime library path using whatever mechanism Solaris
> > > ld.so provides.
> >
> > I think this is a workaround when where configure should do the work.
>
> I really don't think it is. :)
>
> So, you have installed OpenSSL's shared libraries into /usr/foo/lib.
> Instead of making a one-time modification to your runtime linker
> configuration (or adding a LD_LIBRARY_PATH/LD_RUN_PATH to your
> ~/.profile, etc etc), you want every application to add stuff to it's
> ./configure script, to make it work for you. Hmmmm. ;)

Both openssh and wget thought I was important enough to do this ;)

Seriously, they both compile and link on Solaris against openssl in
non-standard locations without setting LD_LIBRARY_PATH, LD_RUN_PATH or
LDFLAGS. So it's odd that neon doesn't do this. Given that no code has
to be written but just copied from either package, what is the hesitancy
to put this in neon?

It also appears that openssh uses -R for NetBSD builds, so two birds
could be handled with one stone.

Setting LD_RUN_PATH when running configure on Solaris systems does not
work, because other -R paths are being passed to the linker when
running configure.

% man ld
...
     LD_RUN_PATH
           An alternative mechanism for specifying a runpath to
           the link-editor (see -R option). If both LD_RUN_PATH
           and the -R option are specified, -R supersedes.

Using LD_LIBRARY_PATH is not an ideal solution. Managing this is harder
for a large numbers of systems and users have to modify their .login/.profile
to add paths to LD_LIBRARY_PATH. I know that you can edit each system's
/etc/{.profile,.login}, but I've also had users that have their own
.login's and .profiles that reset LD_LIBRARY_PATH. So in the end this is more
work than just compiling the program to find the .so's at runtime.

In the end this isn't a big deal, but it would be nice and make it easier
for us Solaris users.

Best,
Blair

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:08 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.