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

svn1.6.2 compile problem on Ubuntu 9.04

From: warking <warking.net_at_gmail.com>
Date: Wed, 20 May 2009 23:25:34 +0800

Hi all,
I just downloaded subversion-1.6.2 source tarball from the official svn site
and installed all deps according to the INSTALL file through ubuntu's
apt-get.
My system is Ubuntu 9.04 x64. After that, I run ./configure ( with no
additional parameters). Here's its output:

configure: Configuring Subversion 1.6.2
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 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... gcc -E
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-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
configure: Apache Portable Runtime (APR) library configuration
checking for APR... yes
checking APR version... 1.2.12
configure: Apache Portable Runtime Utility (APRUTIL) library configuration
checking for APR-util... yes
checking APR-UTIL version... 1.2.12
checking for pkg-config... /usr/bin/pkg-config
configure: checking neon library
checking neon library version... 0.28.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
configure: looking for apr_memcache as part of apr-util
checking apr_memcache.h usability... no
checking apr_memcache.h presence... no
checking for apr_memcache.h... no
checking for Apache module support via DSO through APXS... no
==================================================================
WARNING: skipping the build of mod_dav_svn
         try using --with-apxs
==================================================================
configure: checking sqlite library
amalgamation not found at
/data/Downloads/subversion-1.6.2/sqlite-amalgamation/sqlite3.c
checking sqlite3.h usability... yes
checking sqlite3.h presence... yes
checking for sqlite3.h... yes
checking sqlite library version (via header)... okay
checking for sqlite3_close in -lsqlite3... 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 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... 1572864
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... yes
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 -m elf_x86_64) 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 -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) 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 -m elf_x86_64) 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... yes
checking sasl/sasl.h presence... yes
checking for sasl/sasl.h... yes
checking sasl/saslutil.h usability... yes
checking sasl/saslutil.h presence... yes
checking for sasl/saslutil.h... yes
checking for prop_get in -lsasl2... yes
checking for availability of Cyrus SASL v2... yes
checking for Mac OS KeyChain Services... no
checking whether APR has support for DSOs... yes
checking for D-Bus .pc file... no
checking whether to look for GNOME Keyring... no
checking for msgfmt... /usr/bin/msgfmt
checking for msgmerge... /usr/bin/msgmerge
checking for xgettext... /usr/bin/xgettext
checking for library containing bindtextdomain... none required
checking for bind_textdomain_codeset... yes
checking if we are using GNU gettext... yes
checking whether to look for KWallet... no
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... no
checking for perl... /usr/bin/perl
checking for ruby... /usr/bin/ruby
checking for rb_hash_foreach()... yes
checking for rdoc... /usr/bin/rdoc
checking for Ruby major version... 1
checking for Ruby minor version... 9
checking for swig... none
configure: Configuring python swig binding
checking for Python includes... -I/usr/include/python2.6
checking for compiling Python extensions... gcc -pthread -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... 5010000
configure: Configuring Ruby SWIG binding
checking for Ruby include path... -I. -I/usr/include/ruby-1.9.0
-I/usr/include/ruby-1.9.0/ruby -I/usr/include/ruby-1.9.0/ruby/backward
-I/usr/include/ruby-1.9.0/x86_64-linux
checking how to compile Ruby extensions... cc -g -O2 -pthread
checking how to link Ruby extensions... cc -shared -shrext .so
checking for linking Ruby libraries... -lruby1.9
checking for rb_errinfo... yes
checking where to install Ruby scripts... /usr/local/lib/site_ruby/1.9.0
checking where to install Ruby extensions...
/usr/local/lib/site_ruby/1.9.0/x86_64-linux
checking how to use output level for Ruby bindings tests... normal
checking for ctypesgen.py... none
configure: creating ./config.status
config.status: creating Makefile
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 contrib/hook-scripts/commit-email.pl
config.status: creating tools/hook-scripts/commit-access-control.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 svn_private_config.h commands

That's a little bit verbose, but I think everything's OK except the red
line. The configure script didn't generate a proper
subversion/svn_private_config.h file. I checked that generated file. Its
size is zero. The script just created a blank header file for me. After I
was aware of this. I copied the file from one of my collegues(whose system
is the same as mine, but after he ran the configure script, there was no the
red line in the output but a perfect header file in position) , a 5K header
file and then the compilation process goes perfect. Finally I got my self
compiled lastest svn-1.6.2 and it works fine. But for now, I am still
confused of that problem. Why can't I generate a proper header file?

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2331596

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-20 17:28:00 CEST

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

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