Ubuntu: Subversion 1.5.1 with ssl

Hi,

ich hab Probleme bei der Installation von Subversion 1.5.1 unter Ubuntu mit SSL Support. In dem INSTALL file steht ./configure --with-ssl und vom Output her würde ich sagen alles ist okay:

Code:
mathias@localhost:~/Desktop/subversion-1.5.1$ ./configure --with-ssl
configure: Configuring Subversion 1.5.1
configure: creating config.nice
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether ln -s works... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for static Apache module support... no
checking for Apache module support via DSO through APXS... no
==================================================================
WARNING: skipping the build of mod_dav_svn
         --with-apxs or --with-apache must be used
==================================================================
configure: Apache Portable Runtime (APR) library configuration
checking for APR... yes
checking APR version... 1.2.11
configure: Apache Portable Runtime Utility (APRUTIL) library configuration
checking for APR-util... yes
checking APR-UTIL version... 1.2.12
configure: checking neon library
checking for neon-config... /usr/bin/neon-config
checking neon library version... 0.27.2
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
configuring libtool now
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognize dependent libraries... pass_all
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking whether libtool needs -no-undefined... no
checking whether to avoid circular linkage at all costs... no
checking for trang... none
checking for socket in -lsocket... no
checking for availability of Berkeley DB... no
checking whether to look for SASL... yes
configure: Looking in default locations
checking sasl/sasl.h usability... no
checking sasl/sasl.h presence... no
checking for sasl/sasl.h... no
checking for availability of Cyrus SASL v2... no
checking for Mac OS KeyChain Services... no
checking for msgfmt... none
checking for msgmerge... none
checking for xgettext... none
checking for ANSI C header files... (cached) yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for working memcmp... yes
checking for vprintf... yes
checking for _doprnt... no
checking for symlink... yes
checking for readlink... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for inflate in -lz... yes
checking for python... /usr/bin/python
checking for JDK... configure: WARNING: no JNI header files found.
no
checking for perl... /usr/bin/perl
checking for ruby... none
checking for swig... none
configure: Configuring python swig binding
checking for Python includes... -I/usr/include/python2.5
checking for compiling Python extensions... gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC
checking for linking Python extensions... gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
checking for linking Python libraries... -Wl,-O1 -Wl,-Bsymbolic-functions
checking for apr_int64_t Python/C API format string... L
checking perl version... 5008008
configure: creating ./config.status
config.status: creating Makefile
config.status: WARNING:  'Makefile.in' seems to ignore the --datarootdir setting
config.status: creating tools/backup/hot-backup.py
config.status: creating contrib/client-side/svn_load_dirs/svn_load_dirs.pl
config.status: creating contrib/client-side/svncopy/svncopy.pl
config.status: creating contrib/client-side/svncopy/testsvncopy.pl
config.status: creating tools/hook-scripts/commit-access-control.pl
config.status: creating tools/hook-scripts/commit-email.pl
config.status: creating subversion/bindings/swig/perl/native/Makefile.PL
config.status: creating packages/solaris/pkginfo
config.status: creating subversion/svn_private_config.h
config.status: subversion/svn_private_config.h is unchanged
config.status: executing mkdir-init commands
configure: WARNING: we have configured without BDB filesystem support


You don't seem to have Berkeley DB version 4.0.14 or newer
installed and linked to APR-UTIL.  We have created Makefiles which
will build without the Berkeley DB back-end; your repositories will
use FSFS as the default back-end.  You can find the latest version of
Berkeley DB here:
  http://www.oracle.com/technology/software/products/berkeley-db/index.html

mathias@localhost:~/Desktop/subversion-1.5.1$

Aber make sagt was anderes:
Code:
mathias@localhost:~/Desktop/subversion-1.5.1$ make
cd subversion/libsvn_ra_neon && /bin/bash /home/mathias/.local/share/Trash/files/subversion-1.5.1/libtool --tag=CC --silent --mode=link gcc  -g -O2  -pipe -Wall -g -O2 -pthread  -D_LARGEFILE64_SOURCE -DNE_LFS   -rpath /usr/local/lib -o libsvn_ra_neon-1.la  commit.lo fetch.lo file_revs.lo get_dated_rev.lo get_location_segments.lo get_locations.lo get_locks.lo lock.lo log.lo merge.lo mergeinfo.lo options.lo props.lo replay.lo session.lo util.lo ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la /usr/lib/libaprutil-1.la  /usr/lib/libapr-1.la -luuid -lrt -lcrypt  -lpthread -ldl /usr/lib/libneon-gnutls.la 
libtool: link: cannot find the library `/usr/lib/libneon-gnutls.la' or unhandled argument `/usr/lib/libneon-gnutls.la'
make: *** [subversion/libsvn_ra_neon/libsvn_ra_neon-1.la] Error 1
mathias@localhost:~/Desktop/subversion-1.5.1$

Was soll ich tun? *ratlos* sei

cu
serow
 
Gibt es Subversion nicht in den Ubuntu-Repos? Oder warum baust du es selbst?

Die Fehlermeldung sagt ja eigentlich schon alles. "/usr/lib/libneon-gnutls.la" gibt es nicht. Also über die Repository ein Paket installieren, das diese Datei bereitstellt (heißt vermutlich "gnutls" oder "gnutls-dev" oder so ähnlich). Oder du schaust, ob diese Datei bei dir woanders liegt. Dann musst du ggf. den Pfad dieser Datei über einen configure-Parameter angeben.

mfg, metax.

~edit:
Offenbar gibt es SVN doch schon in den Ubuntu-Repos: https://help.ubuntu.com/community/Subversion
Da hier auch SSL-Verbindungen zur Verfügung stehen, denke ich auch, dass TLS reinkonfiguriert wurde.
Installier es einfach mit "sudo apt-get install subversion"
 
Doch SVN gibts auch in den Repos aber ich brauche die 1.5.1 Version. Die Repos haben nur 1.4.6 oder so.

Code:
mathias@localhost:~$ locate libneon-gnutls
/usr/lib/libneon-gnutls.a
/usr/lib/libneon-gnutls.so
/usr/lib/libneon-gnutls.so.26
/usr/lib/libneon-gnutls.so.26.0.4
mathias@localhost:~$
Das Zeug is installiert - auch die dev Packete. Aber ein .la File ist da nicht dabei .. Was ist ein .la File? Ideen?

cu serow
 
.la sind libtool-Dateien.

Hast du mal die INSTALL gelesen?
Ich hab mir eben mal die 1.5.1-Quellen runtergeladen und bin in der INSTALL auf folgendes gestoßen:
You need OpenSSL
installed on your system, and you must add "--with-ssl" as a
"./configure" parameter. If your OpenSSL installation is hard
for Neon to find, you may need to use "--with-libs=/path/to/lib"
in addition.
Es könnte also was bringen, noch den Parameter "--with-libs=/usr/lib/libneon-gnutls.so" mit anzuhänge, dann brauchst du die .la-Datei mit etwas Glück nicht mehr.

In meinem Gentoo wird die "--with-ssl" Option gar nicht angesprochen, da gibt es nur die "--with-neon=/usr" Option.

Vielleicht bringt dich das weiter.

Ansonsten solltest du mal schauen, ob es irgendwo einen Backport für dein Betriebssystem gibt.

mfg, metax.
 
Hi,
hat leider keinelei Auswirkungen das --with-libs Argument. Genau dieselbe Fehlermeldung.

Backports gibts aber die haben das neue svn auch nicht :S

cu
serow
 
Zurück
Oben