[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Major upgrades to SWIG/Python bindings in r15848

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2005-08-21 18:27:37 CEST

On Sun, Aug 21, 2005 at 01:13:36AM -0700, Garrett Rooney wrote:
> >>I doubt it. Actually, I'm pretty sure the regular svn unit tests won't
> >>work without a make install either, it's not just the bindings that have
> >>the problem.
> >'make check' works fine for me without a make install on Mac OS X here.
> If you already have a version of Subversion installed into the prefix
> you're building in that could explain why it works for you, the tests
> would be picking up the installed libraries, not the ones that were just
> built.

Well, it certainly _seems_ to work fine. Just to be clear, this is what I've
just tried:

$ pwd
/Users/malcolm
$ curl -Ss -O http://fornix.brain.org/subversion/subversion-1.2.3.tar.bz2
$ md5 subversion-1.2.3.tar.bz2
$ tar jxf subversion-1.2.3.tar.bz2
$ cd subversion-1.2.3
$ ./configure --prefix=/Users/malcolm/usr
$ make
$ make check
$ make install

Everything seemed to work fine, including the tests, and there wasn't any
previous Subversion installation lying around, so it must have picked up
the just-built libraries. (The ~/usr directory didn't even exist until the
make install step ran).

This is a pretty stock Mac OS 10.4.2/Xcode 2.1 installation, so it complained
about Apache, Ruby, and BDB dependencies (and wouldn't build mod_dav_svn,
Ruby bindings, and BDB support respectively), but the resulting tests seemed
to be doing _something_.

Regards,
Malcolm

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 21 18:28:49 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.