Since I'm rebuilding subversion 1.2.3, I decided to make my own python
bindings from source to run Dale Hirt's RepoMerge.py script:
>8) make swig-py
>9) make install-swig-py
...as part of the procedure noted below. Is this procedure order is
correct? Is there a test for these bindings like the 'make check' overall
test?
-Matt
>Date: Tue, 27 Sep 2005 06:21:22 -0500
>To: bob@proulx.com (Bob Proulx)
>From: Matt England <mengland@mengland.net>
>Subject: Re: Minimal build instructions for svnserver & fsfs only?
>Cc: users@subversion.tigris.org,Matt England <mengland@mengland.net>
>
>At 9/26/2005 10:50 PM, Bob Proulx wrote:
>>Because you say you are running on a GNU/Linux and would normally use
>>shared libraries there I would use the following configure options:
>>
>> ./configure --without-berkeley-db
>>
>>Then check the resulting shared libraries that are linked against the
>>svn binary.
>>
>> ldd svn
>
>Ahh, this seems to make sense. Very helpful.
>
>Additionally note: I found (via ldd) I had a ton of dependencies on
>external, old svn/apr/etc libs...and hence I probably need (or at least I
>presume) to update the procedure to delete said libs in advance prior to
>running the build. Updated procedure follows.
>
>Also: I want to run Dale Hirt's (sp?) python script to merge repositories,
>hence I want to install the python bindings. Should I run the 'make
>swig-py' and 'make install-swig-py' commands at the end of the procedure
>as per below?
>
>1) delete the following from <prefix>/lib: libsvn*, libapr*, libneon*
>2) extract the tarball for subversion-x.y.z
>3) cd into subversion-x.y.z
>4) ./configure --without-berkeley-db --prefix=<prefix>
>5) make
>6) make check
>7) make install
>8) make swig-py
>9) make install-swig-py
>
>Unfortunately, this brings down the existing server for the duration of
>the build. No fun, but hence I'm up early in the morning so as to not
>break stuff for my developers.
>
>Is my analysis and procedure correct?
>
>-Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 27 15:20:04 2005