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

shared dav_svn is not relinking

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-04-12 16:02:48 CEST


I notice that the installed libmod_dav_svn.so module is linked to
subversion libraries in my build tree and not to the installed
libraries. Within the build tree, libmod_dav_svn.so is linked against
libraries in the build tree, just like all the other subversion
libraries. However once installed the subversion libraries are linked
against the installed libraries, but libmod_dav_svn.so remains linked
against the build tree.

The file subversion/mod_dav_svn/libmod_dav_svn.la contains a
relink_command, but this does not appear to get executed when
libmod_dav_svn.so is installed. The module is installed by calling
apache's 'apxs -i -a', this in turn calls apache's instdso.sh, and
this simply copies the library from the build tree into the module
directory. Quoting from instdso.sh

  # instdso.sh - install Apache DSO modules
  # we use this instead of libtool --install because:
  # 1) on a few platforms libtool doesn't install DSOs exactly like we'd
  # want (weird names, doesn't remove DSO first)
  # 2) we never want the .la files copied, so we might as well copy
  # the .so files ourselves

it appears that not using libtool is deliberate.

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.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 12 16:03:39 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.