On Feb 16, 2005, at 5:34 PM, James FitzGibbon wrote:
> Are you certain that 'trac-admin' is using your installed svn binaries,
> rather than using ones that it ships with that are pre-FSFS?
> Or is trac-admin a binary that is statically linked against svn libs
> don't support FSFS?
> Either circumstance would cause this type of error.
trac-admin is a python script, that uses svn via the afore mentioned
swig py23 svn bindings. Those bindings may well be the problem, as they
are being installed separately with fink, then copied over to standard
python installation. You can see the source of the version of the
script that I am using at:
I have just tried to install those bindings without fink, by fllowing
the procedure detailed in:
I configure swig with:
$ ./configure --with-python=/usr/bin/python
Swig itself seems to install OK... and it is the swig that the
subversion configure script picks up.
I configure subversion with
$ ./configure --without-berkeley-db PYTHON=/usr/bin/python
and it seems to build ok, but gives the following warning when
*** Warning: This system can not link to static lib archive
*** I have the capability to make that library automatically link in
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
Plus, it does not a /usr/local/lib/libsvn_swig_py.so as claimed...
Thus, trying to build swig-py as described, fails:
$ make swig-py
--silent --mode=compile -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK
swig/python/libsvn_swig_py -prefer-pic -c -o
libtool: unrecognized option `-DDARWIN'
Try `libtool --help' for more information.
make: *** [subversion/bindings/swig/python/svn_client.lo] Error 1
Any ideas anyone?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Feb 16 19:04:19 2005