I tried compiling and installing r925154 and got in the install step:
$ ../configure --enable-maintainer-mode --enable-debug
$ make install
svn: Working copy format of '/home/jens/Programme/subversion/svn.trunk' is
too old (9); please run 'svn upgrade'
It's not easy to see that the install was succesful. Using option -d of make
reveals that this message is created in the "revision-install" target and
was sucessfully created.
Nevertheless I suggest to print an explaining message before this or to
redirect the error message to /dev/null.
I also miss JavaHL stuff. Where is it installed?
Ah, searching in the Makefile I found the target "install-javahl". Why isn't
this called from "install"?
Mhm, I may be wrong but I think the build system improved a lot. In the past
I had to follow a > 30 lines guide specifying a special order of
subversions components to build and install, to sometimes use -j1, to call
various make targets, settings LD_LIBRARY_PATH in the middle of install, ...
But this time I skipped Python and Perl bindings.
A further problem: neon is not searched by default if no --with-neon flag is
given (but there is a output "configure: checking neon library"). Why doesn't
configure search for it by default? So I have no http access!
Only after playing with the neon test in configure I get:
"An appropriate version of neon could not be found, so libsvn_ra_neon
will not be built. If you want to build libsvn_ra_neon, please
install neon 0.29.0 on this system."
Do I need version 0.29.0? This isn't documented in INSTALL!
PS: Here is a small patch for INSTALL. autogen.sh is by default executable,
no need to do it again, right?
--- INSTALL (Revision 925154)
+++ INSTALL (Arbeitskopie)
@@ -728,7 +728,6 @@
$ svn co https://svn.apache.org/repos/asf/subversion/trunk svn
$ cd svn
$ # get neon/apr as required
- $ chmod +x autogen.sh
$ mkdir ../obj
$ cd ../obj
PS: Please CC: me.
Received on 2010-03-19 17:14:33 CET