On Wed, 21 Jul 2004, Travis P wrote:
> Date: Wed, 21 Jul 2004 20:18:25 -0500
> From: Travis P <firstname.lastname@example.org>
> To: svn Dev <email@example.com>, Max Bowsher <firstname.lastname@example.org>
> Subject: Re: Request for another OS X test build
> On Jul 21, 2004, at 8:08 PM, Travis P wrote:
> > On Jul 21, 2004, at 7:24 AM, Max Bowsher wrote:
> >> My attempts to use public access OS X machines in my university
> >> computer
> >> rooms for svn testing have failed, because they don't have a C
> >> compiler :-(
> > That's crazy sad. Maybe they just never had it requested? Maybe
> > worth asking.
> >> Therefore, please could Christian, or someone else with access to OS
> >> X, try
> >> to build (and install) the python (and perl too if possible) bindings
> >> using
> >> subversion from the 1.1.x branch, but with r10371 merged from trunk.
> >> *Hopefully*, that will fix the bindings on OS X.
> >> Max.
> > I gave this a shot on my 10.3.4 system. I didn't encounter library
> > errors. You can look at the details of what I did below and see if
> > my build adequately tested your update. I obviously abbreviated a lot
> > of data and am not familiar with the 'make check' reporting system, so
> > you'll see I talk about what I saw, some of which may very well be
> > non-issues.
> > % svn co http://svn.collab.net/repos/svn/branches/1.1.x svn-1.1
> > % svn merge -r10370:10371 http://svn.collab.net/repos/svn/trunk .
> > % ./configure --enable-maintainer-mode --enable-swig-bindings=all
> > --prefix=/tmp/testinstall
> > ...
> > configure: Enabled swig binding: perl
> > configure: Enabled swig binding: python
> > configure: Enabled swig binding: java
> > checking for swig... none
> > ....
> > Neon, Apache 2, and BDB were not found found,
> > so the DAV access layer and BDB FS were not
> > built.
> > % make
> > % make check
> > % make install
> > Ran a couple simple commands (using the newly installed svn client)
> > against the wc in which I built (status, log) and they worked okay.
> > The check had a bunch of failures:
> > Running all tests in basic_tests.py...FAILURE
> > Running all tests in commit_tests.py...FAILURE
> > Running all tests in update_tests.py...FAILURE
> > ....
> > The tests.log didn't seem to give much data.
> > But then it looks like they were re-evaluated and skipped?
> > SKIP: basic_tests.py 1: basic checkout of a wc
> > SKIP: basic_tests.py 2: basic status command
> > SKIP: basic_tests.py 3: basic commit command
> > SKIP: basic_tests.py 4: basic update command
> > SKIP: basic_tests.py 5: basic mkdir URL
> > I've wondered this before and it is relevant to this case: given an
> > svn installation, how does one tell if the bindings were built and
> > installed?
> > -Travis
> Oops, forgot to mention that before configure, I ran autogen.sh as
> INSTALL instructed.
> % sh ./autogen.sh
> buildcheck: checking installation...
> buildcheck: autoconf version 2.57 (ok)
> buildcheck: autoheader version 2.57 (ok)
> buildcheck: libtool version 1.5 (ok)
> Copying libtool helper: /usr/share/aclocal/libtool.m4
I was able to build subversion-1.1.0-rc1 on MAC OS X 10.3.4 last night
with the following commands:
$ ./configure --with-ssl
However "make check" failed on a lot of tests (SKIP) starting with
This was without BDB accessible.
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jul 22 17:49:05 2004