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

Re: shared dav_svn is not relinking

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-04-12 18:50:36 CEST

"Sander Striker" <striker@apache.org> writes:

> > If I execute the relink_command by hand I get a shared library that is
> > correctly linked against the installed Subversion libraries.
> >
> > Does anyone else see this problem? How is it supposed to work? Is this
> > an Apache bug?
> >
> > I am using apache-2.0.35 and libtool-1.4.2 on Linux.
> I browsed the modules modules.mk files and came across (for example dav):
> mod_dav.la: mod_dav.slo props.slo util.slo util_lock.slo liveprop.slo providers.slo std_liveprop.slo
> $(SH_LINK) -rpath $(libexecdir) -module -avoid-version mod_dav.lo props.lo util.lo util_lock.lo liveprop.lo providers.lo
> std_liveprop.lo
> It seems the -rpath option is goodness here. Would that solve our problem?

There is already an '-rpath /usr/local/subversion/lib' when I link
libmod_dav_svn.so. That doesn't look right since this is going to get
installed in the apache modules directory not the subversion
directory, however I don't think that is the problem or the
solution. The problem is that the libtool produced library needs to be
relinked on installation and that is not happening.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 12 18:51:28 2002

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.