You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Bradley Wagner <br...@hannonhill.com> on 2006/06/02 20:29:19 UTC
Installing Apache modules only
I have installed subversion already. The binaries are there and
functioning correctly. Now I'd like to go back with the source the I
kept and simply install the apache modules and nothing else. Is there
any way to do this without overwriting my existing installation of
the binaries and libraries? Is there any way to tell configure to
only build the apache *.so files?
Thanks,
Bradley
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Bradley Wagner <br...@hannonhill.com>.
That said, do you think there is anyway to re-locate the svn
installation without borking the apache modules?
On Jun 4, 2006, at 7:47 PM, Ryan Schmidt wrote:
> On Jun 5, 2006, at 00:43, Bradley Wagner wrote:
>
>> Come to think of it how do the modules know where to locate the
>> subversion libraries? Is that path hardcoded into the modules? I
>> have two svn installations right now. 1.3.1 is installed in /usr/
>> local and 1.3.2 installed property at /usr/local/svn-1.3.2/. Is
>> there any way to test to see which of those installations my
>> apache modules are using?
>
> I believe that yes, generally the module would be dynamically
> linked with specific Subversion libraries. You should be able to
> find out which ones by using ldd (or on Mac OS X: otool -L). For
> example I get:
>
> $ otool -L /opt/local/apache2/modules/mod_dav_svn.so
> /opt/local/apache2/modules/mod_dav_svn.so:
> /opt/local/lib/libsvn_repos-1.0.dylib (compatibility
> version 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_fs-1.0.dylib (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_fs_fs-1.0.dylib (compatibility
> version 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_delta-1.0.dylib (compatibility
> version 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_subr-1.0.dylib (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libaprutil-1.0.dylib (compatibility version
> 3.0.0, current version 3.7.0)
> /opt/local/lib/libexpat.1.dylib (compatibility version
> 7.0.0, current version 7.0.0)
> /opt/local/lib/libapr-1.0.dylib (compatibility version
> 3.0.0, current version 3.7.0)
> /opt/local/lib/libiconv.2.dylib (compatibility version
> 6.0.0, current version 6.0.0)
> /opt/local/lib/libintl.3.dylib (compatibility version
> 8.0.0, current version 8.3.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
> current version 88.1.5)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Erik Huelsmann <eh...@gmail.com>.
On 6/6/06, Bradley Wagner <br...@hannonhill.com> wrote:
> Given this, is there any way to un-link and re-link these modules to
> a different set of SVN libraries. If not, I don't think Erik's
> strategy of installing SVN into a separate directory and removing
> that directory when it's done would work (earlier in this thread),
> right?
That's exactly what DESTDIR installs are about. You use ./configure
--prefix=/usr/local; then make install DESTDIR=/opt/svn; the binaries
saved in /opt/svn are built as if they are in /usr/local, meaning you
can't use them until they're actually in that location. So, in effect,
they are linked against the already installed ones :-)
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Bradley Wagner <br...@hannonhill.com>.
Given this, is there any way to un-link and re-link these modules to
a different set of SVN libraries. If not, I don't think Erik's
strategy of installing SVN into a separate directory and removing
that directory when it's done would work (earlier in this thread),
right?
Bradley
On Jun 5, 2006, at 11:15 AM, Muthaiah Ramanathan wrote:
>> I believe that yes, generally the module would be
>> dynamically linked
>> with specific Subversion libraries. You should be
>> able to find out
>> which ones by using ldd (or on Mac OS X: otool -L).
>> For example I get:
>>
>> $ otool -L /opt/local/apache2/modules/mod_dav_svn.so
>> /opt/local/apache2/modules/mod_dav_svn.so:
>> /opt/local/lib/libsvn_repos-1.0.dylib
>> (compatibility version
>> 1.0.0, current version 1.0.0)
>> /opt/local/lib/libsvn_fs-1.0.dylib
>> (compatibility version
>> 1.0.0, current version 1.0.0)
>> /opt/local/lib/libsvn_fs_fs-1.0.dylib
>> (compatibility version
>> 1.0.0, current version 1.0.0)
>> /opt/local/lib/libsvn_delta-1.0.dylib
>> (compatibility version
>> 1.0.0, current version 1.0.0)
>> /opt/local/lib/libsvn_subr-1.0.dylib
>> (compatibility version
>> 1.0.0, current version 1.0.0)
>> /opt/local/lib/libaprutil-1.0.dylib
>> (compatibility version
>> 3.0.0, current version 3.7.0)
>> /opt/local/lib/libexpat.1.dylib
>> (compatibility version
>> 7.0.0, current version 7.0.0)
>> /opt/local/lib/libapr-1.0.dylib
>> (compatibility version
>> 3.0.0, current version 3.7.0)
>> /opt/local/lib/libiconv.2.dylib
>> (compatibility version
>> 6.0.0, current version 6.0.0)
>> /opt/local/lib/libintl.3.dylib
>> (compatibility version 8.0.0,
>> current version 8.3.0)
>> /usr/lib/libSystem.B.dylib (compatibility
>> version 1.0.0,
>> current version 88.1.5)
> Yes, as Ryan said, it is possible to see to which
> modules your Subversion app is linked to, using ldd
> (on U*x):
>
> On my system it looks like this:
>
> -bash-3.00# ldd
> /lnx_data/apache2.0.54/modules/mod_dav_svn.so | grep
> libapr
>
> libaprutil-1.so.0 =>
> /lnx_data/apache2.0.54/lib/libaprutil-1.so.0
> (0xb7dca000)
> libapr-1.so.0 =>
> /lnx_data/apache2.0.54/lib/libapr-1.so.0 (0xb7d34000)
>
> -bash-3.00# ldd /lnx_data/apache2.0.54/bin/httpd |
> grep libapr
> libaprutil-1.so.0 =>
> /lnx_data/apache2.0.54/lib/libaprutil-1.so.0
> (0xb7f06000)
> libapr-1.so.0 =>
> /lnx_data/apache2.0.54/lib/libapr-1.so.0 (0xb7ee4000)
>
> /Ram
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Muthaiah Ramanathan <ra...@yahoo.com>.
> I believe that yes, generally the module would be
> dynamically linked
> with specific Subversion libraries. You should be
> able to find out
> which ones by using ldd (or on Mac OS X: otool -L).
> For example I get:
>
> $ otool -L /opt/local/apache2/modules/mod_dav_svn.so
> /opt/local/apache2/modules/mod_dav_svn.so:
> /opt/local/lib/libsvn_repos-1.0.dylib
> (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_fs-1.0.dylib
> (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_fs_fs-1.0.dylib
> (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_delta-1.0.dylib
> (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_subr-1.0.dylib
> (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libaprutil-1.0.dylib
> (compatibility version
> 3.0.0, current version 3.7.0)
> /opt/local/lib/libexpat.1.dylib
> (compatibility version
> 7.0.0, current version 7.0.0)
> /opt/local/lib/libapr-1.0.dylib
> (compatibility version
> 3.0.0, current version 3.7.0)
> /opt/local/lib/libiconv.2.dylib
> (compatibility version
> 6.0.0, current version 6.0.0)
> /opt/local/lib/libintl.3.dylib
> (compatibility version 8.0.0,
> current version 8.3.0)
> /usr/lib/libSystem.B.dylib (compatibility
> version 1.0.0,
> current version 88.1.5)
Yes, as Ryan said, it is possible to see to which
modules your Subversion app is linked to, using ldd
(on U*x):
On my system it looks like this:
-bash-3.00# ldd
/lnx_data/apache2.0.54/modules/mod_dav_svn.so | grep
libapr
libaprutil-1.so.0 =>
/lnx_data/apache2.0.54/lib/libaprutil-1.so.0
(0xb7dca000)
libapr-1.so.0 =>
/lnx_data/apache2.0.54/lib/libapr-1.so.0 (0xb7d34000)
-bash-3.00# ldd /lnx_data/apache2.0.54/bin/httpd |
grep libapr
libaprutil-1.so.0 =>
/lnx_data/apache2.0.54/lib/libaprutil-1.so.0
(0xb7f06000)
libapr-1.so.0 =>
/lnx_data/apache2.0.54/lib/libapr-1.so.0 (0xb7ee4000)
/Ram
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jun 5, 2006, at 00:43, Bradley Wagner wrote:
> Come to think of it how do the modules know where to locate the
> subversion libraries? Is that path hardcoded into the modules? I
> have two svn installations right now. 1.3.1 is installed in /usr/
> local and 1.3.2 installed property at /usr/local/svn-1.3.2/. Is
> there any way to test to see which of those installations my apache
> modules are using?
I believe that yes, generally the module would be dynamically linked
with specific Subversion libraries. You should be able to find out
which ones by using ldd (or on Mac OS X: otool -L). For example I get:
$ otool -L /opt/local/apache2/modules/mod_dav_svn.so
/opt/local/apache2/modules/mod_dav_svn.so:
/opt/local/lib/libsvn_repos-1.0.dylib (compatibility version
1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_fs-1.0.dylib (compatibility version
1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_fs_fs-1.0.dylib (compatibility version
1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_delta-1.0.dylib (compatibility version
1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_subr-1.0.dylib (compatibility version
1.0.0, current version 1.0.0)
/opt/local/lib/libaprutil-1.0.dylib (compatibility version
3.0.0, current version 3.7.0)
/opt/local/lib/libexpat.1.dylib (compatibility version
7.0.0, current version 7.0.0)
/opt/local/lib/libapr-1.0.dylib (compatibility version
3.0.0, current version 3.7.0)
/opt/local/lib/libiconv.2.dylib (compatibility version
6.0.0, current version 6.0.0)
/opt/local/lib/libintl.3.dylib (compatibility version 8.0.0,
current version 8.3.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 88.1.5)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Bradley Wagner <br...@hannonhill.com>.
Come to think of it how do the modules know where to locate the
subversion libraries? Is that path hardcoded into the modules? I have
two svn installations right now. 1.3.1 is installed in /usr/local and
1.3.2 installed property at /usr/local/svn-1.3.2/. Is there any way
to test to see which of those installations my apache modules are using?
Bradley
On Jun 4, 2006, at 6:30 PM, Bradley Wagner wrote:
> Hmm. I guess that's as good as it gets. Is DESTDIR the destination
> for the svn installation or the modules directory? Are the apache
> modules somehow linked to the location of the subversion
> installation. So if I go moving around the modules and removing the
> duplicate subversion install, will that mess anything up?
>
> Bradley
>
> On Jun 4, 2006, at 5:49 AM, Erik Huelsmann wrote:
>
>> On 6/2/06, Bradley Wagner <br...@hannonhill.com> wrote:
>>> I have installed subversion already. The binaries are there and
>>> functioning correctly. Now I'd like to go back with the source the I
>>> kept and simply install the apache modules and nothing else. Is
>>> there
>>> any way to do this without overwriting my existing installation of
>>> the binaries and libraries? Is there any way to tell configure to
>>> only build the apache *.so files?
>>
>> No, but you could do a DESTDIR install (make install DESTDIR=....)
>> installing to another dir than the one your install is currently
>> located. After that, you can copy the apache modules to their real
>> directories and remove the destdir.
>>
>> HTH,
>>
>> Erik.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Bradley Wagner <br...@hannonhill.com>.
Hmm. I guess that's as good as it gets. Is DESTDIR the destination
for the svn installation or the modules directory? Are the apache
modules somehow linked to the location of the subversion
installation. So if I go moving around the modules and removing the
duplicate subversion install, will that mess anything up?
Bradley
On Jun 4, 2006, at 5:49 AM, Erik Huelsmann wrote:
> On 6/2/06, Bradley Wagner <br...@hannonhill.com> wrote:
>> I have installed subversion already. The binaries are there and
>> functioning correctly. Now I'd like to go back with the source the I
>> kept and simply install the apache modules and nothing else. Is there
>> any way to do this without overwriting my existing installation of
>> the binaries and libraries? Is there any way to tell configure to
>> only build the apache *.so files?
>
> No, but you could do a DESTDIR install (make install DESTDIR=....)
> installing to another dir than the one your install is currently
> located. After that, you can copy the apache modules to their real
> directories and remove the destdir.
>
> HTH,
>
> Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Installing Apache modules only
Posted by Erik Huelsmann <eh...@gmail.com>.
On 6/2/06, Bradley Wagner <br...@hannonhill.com> wrote:
> I have installed subversion already. The binaries are there and
> functioning correctly. Now I'd like to go back with the source the I
> kept and simply install the apache modules and nothing else. Is there
> any way to do this without overwriting my existing installation of
> the binaries and libraries? Is there any way to tell configure to
> only build the apache *.so files?
No, but you could do a DESTDIR install (make install DESTDIR=....)
installing to another dir than the one your install is currently
located. After that, you can copy the apache modules to their real
directories and remove the destdir.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org