How, specifically, did fink fail? I just installed it on my eMac in the
wee hours of last night. I was installing from scratch, but here's what
I did (this is under 10.2.6, mind):
Installed Apple's X11 and sdk.
Installed the fink package 0.5.3, and copied fink commander into my
applications folder out of the dmg as well.
Installed (with fink commander) the virtual package system-xfree86
(which shouldn't matter, for svn).
Used fink commander to turn on (via preferences...) use of unstable
packages and unstable crypto packages.
Went back to the command line and ran "fink selfupdate-cvs".
Ran "fink install svn-ssl", which wants to install 60 packages.
The computer eventually errors out because it can't find ruby-dev,
having just installed ruby18-dev etc.
I went back into Fink Commander and installed the (archived) ruby-dev.
I ran "fink install svn-ssl" again, which wants to now install 12
packages and eventually completed with a warning message about the
repository format changing back at 0.28
I haven't actually tried running apache or svn, but it looked like it
installed properly. Fink can be temperamental but often it's just a
matter of going and providing it the particular package it wants. On
the other hand, I've built svn by hand under Mac OS X without having
fink on my computer at all, and mostly it's a big hassle to do so and
then when a new version comes out it's a big hassle _all over again_. I
recommend giving fink another go before you get too far along with
building it by hand.
hamilton
On Friday, October 3, 2003, at 02:56 AM, Winston Wolff wrote:
> I am having a lot of trouble getting subversion running. I used to
> have v0.19.?? which I installed with fink. I tried fink yesterday and
> it failed miserably so I am trying to do it manually now and I get the
> following error when I run svn from the bootstrap tarball:
>
> dyld: svn version mismatch for library:
> /Users/winstonw/Downloads/subversion-0.30.0/apr-util/xml/expat/lib/
> .libs/libexpat.0.dylib (compatibility version of user: 5.0.0 greater
> than library's version: 2.0.0)
> Trace/BPT trap
>
> Here are the steps I have done. I am on Mac OS X 10.2.6.
> • Downloaded Berkeley DB4.1.25, built, and installed into
> /usr/local/BerkeleyDB.4.1
> • Dowloaded the v0.30.0 tarball
> • % ./configure --enable-maintainer-mode
> --with-berkeley-db=/usr/local/BerkeleyDB.4.1/ --with-ssl
> • % make # which seemed to work OK
> • % make check # which gave this output:
> Running all tests in config-test...success
> Running all tests in diff-diff3-test...success
> Running all tests in hashdump-test...success
> Running all tests in path-test...success
> Running all tests in random-test...success
> Running all tests in stream-test...success
> Running all tests in string-test...success
> Running all tests in time-test...success
> Running all tests in translate-test...success
> Running all tests in target-test.py...success
> Running all tests in run-fs-tests.py...success
> Running all tests in run-repos-tests.py...success
> Running all tests in getopt_tests.py...FAILURE
> Running all tests in basic_tests.py...FAILURE
> Running all tests in commit_tests.py...FAILURE
> Running all tests in update_tests.py...FAILURE
> Running all tests in switch_tests.py...FAILURE
> Running all tests in prop_tests.py...FAILURE
> Running all tests in schedule_tests.py...FAILURE
> Running all tests in log_tests.py...FAILURE
> Running all tests in copy_tests.py...FAILURE
> Running all tests in diff_tests.py...FAILURE
> Running all tests in export_tests.py...FAILURE
> Running all tests in externals_tests.py...FAILURE
> Running all tests in merge_tests.py...FAILURE
> Running all tests in stat_tests.py...FAILURE
> Running all tests in trans_tests.py...FAILURE
> Running all tests in svnadmin_tests.py...FAILURE
> Running all tests in svnlook_tests.py...FAILURE
> Running all tests in svnversion_tests.py...FAILURE
> At least one test FAILED, checking
> /Users/winstonw/Downloads/subversion-0.30.0/tests.log
> FAIL: getopt_tests.py 1: run svn with no arguments
> FAIL: getopt_tests.py 2: run svn --version
> FAIL: getopt_tests.py 3: run svn --version --quiet
> FAIL: getopt_tests.py 4: run svn --help
> FAIL: getopt_tests.py 5: run svn help
> FAIL: getopt_tests.py 6: run svn help --version
> FAIL: getopt_tests.py 7: run svn help bogus-cmd
> FAIL: getopt_tests.py 8: run svn help log switch
> FAIL: basic_tests.py 1: basic checkout of a wc
> FAIL: commit_tests.py 1: commit one file
> FAIL: update_tests.py 1: update a locally-modified binary file
> FAIL: switch_tests.py 1: test some basic switching operations
> FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel)
> FAIL: schedule_tests.py 1: schedule: add some files
> FAIL: log_tests.py 1: 'svn log', no args, top of wc
> FAIL: copy_tests.py 1: basic copy and move commands -- on files only
> FAIL: diff_tests.py 1: update a file
> FAIL: export_tests.py 1: export an empty directory
> FAIL: externals_tests.py 1: test checkouts with externals
> FAIL: merge_tests.py 1: performing a merge, with mixed results
> FAIL: stat_tests.py 1: status on unversioned file in current directory
> FAIL: trans_tests.py 1: commit new files with keywords active from
> birth
> FAIL: svnadmin_tests.py 1: 'svnadmin dump' on copied directory
> FAIL: svnlook_tests.py 1: test 'svnlook youngest' subcommand
> FAIL: svnversion_tests.py 1: test 'svnversion' on wc and other dirs
> make: *** [check] Error 1
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 3 18:41:09 2003