On 1 Sep 2006, at 19:13, Blake Winton wrote:
> Jeremy Pereira wrote:
> Thank you replying, I was starting to think that I would never get
> it working, so hearing from someone who's able to build it cleanly
> is a huge boost to my morale.
>> I've had a go at this myself to see if I have any problems, but it
>> all seemed to work.
>> My Swig config string is:
>> ./configure --with-python=/usr/bin/python
> Okay, the first thing that I've noticed that's different between
> our setups is that I'm using MacPython (so that I can import
> AppKit, and WebKit, and all sorts of other AppleScript goodies),
> which puts itself in /Library/Frameworks/Python.framework/Versions/
Is that different from the Python that comes bundled with Mac OS X?
My /usr/bin/python is merely a symlink to /System/Library/Frameworks/
>> My Subversion config string is:
>> ./configure PYTHON=/usr/bin/python \
>> --with-apxs=/usr/local/apache2/bin/apxs \
>> --with-berkeley-db=/usr/local/BerkeleyDB.4.3 \
>> --with-ssl --with-editor=vi \
>> Again, don't know if I need the PYTHON=... bit
> Since I'm not using berkeley-db, and I have python in a different
> location, I used a slightly different config string, but mostly the
>> I got the below warnings in the subversion configuration which I
>> thought was quite amusing...
>> configure: WARNING: Detected SWIG version 1.3.29
>> configure: WARNING: This is not compatible with Subversion
>> configure: WARNING: Subversion can use SWIG version 1.3.24 or later
>> During make swig-py I got some further warnings:
> And here's the second place we seem to differ.
> After I did the ./configure step, I did a "make && make check"
> step, which seemed to work okay, but then "sudo make install"
> complained about
> cp .libs/libapr-0.0.9.7.dylib /usr/local/apr/lib/libapr-0.0.9.7.dylib
> cp: /usr/local/apr/lib/libapr-0.0.9.7.dylib: Too many levels of
> symbolic links
That looks like you've already got a broken apr install in place.
Others on the list might be able to shed some light on that, but I'd
start by clearing out everything that Subversion installs and running
> Do I need to be root to run ./configure or make or make check?
>> I haven't actually tested the swig bindings because I know nothing
>> about Python programming. If you'd like to give me a small Python
>> script that exercises the swig libraries, I'll see if they work
> Hopefully, you can just run:
> python -c "import svn"
OK that works fine for me. Do you want my binaries :)
> and if it doesn't complain about something like:
> Traceback (most recent call last):
> File "<string>", line 1, in ?
> ImportError: No module named svn
> you should be good.
> Thanks again,
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Sep 2 01:02:06 2006