Ben Collins-Sussman <sussman <at> collab.net> writes:
>
>
> On Jun 15, 2005, at 4:53 AM, Gal Aviel wrote:
> >
> > (a) create a statically linked 'svn' cmdline client, so I can put
> > it somewhere
> > on a network drive for all the users, and
> >
> > (b) build the required mod_dav_svn Apache module, so I can upgrade
> > my apache to
> > use subversion 1.2.
> >
> > It appears, that (a) is mutually exclusive with (b)
>
> The INSTALL file has always stated:
>
> Note: do *not* configure subversion with "--disable-shared"!
> mod_dav_svn *must* be built as a shared library, and it will
> look for other libsvn_*.so libraries on your system.
>
> So yes, the two options are mutually exclusive, and always have been.
>
> My recommendation is to build everything shared, so that
> mod_dav_svn.so and libsvn_*.so are installed on the server. Then to
> create a static client, reconfigure with --enable-all-static.
>
I think my confusion stems from the fact that I assumed for some reason
(probably because that's how I wanted things to look) that (from configur e
--help) "building completely stand alone binaries" means "building completely
stand alone programs (svn, svnserve, etc)". Binaries didn't associated with
libraries for me, but rather with programs. I figured that using
'--enable-all-staitc' just creates statically linked programs, but dynamic
libraries are still produced.
Well no bug reprot this time.
Thanks again for the clarification,
Gal.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 16 09:58:15 2005