LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   SVN compile issues - centos 5 64bit (https://www.linuxquestions.org/questions/linux-server-73/svn-compile-issues-centos-5-64bit-597538/)

neocontrol 11-06-2007 10:55 AM

SVN compile issues - centos 5 64bit
 
Hi Everyone,

I'm trying to compile SVN 1.4.5 on CentOS5 64bit.

The configure appears to go okay

Code:

./configure --prefix=/usr/local/subversion --with-apr-util=/usr/local/apache2 --with-apr=/usr/local/apache2

configure: Configuring Subversion 1.4.5
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 ANSI C... none needed
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 egrep... 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... found at /usr/local/apache2/bin/apxs
checking httpd version... recent enough
configure: Apache Portable Runtime (APR) library configuration
checking for APR... yes
checking APR version... 1.2.8
configure: Apache Portable Runtime Utility (APRUTIL) library configuration
checking for APR-util... yes
checking APR-UTIL version... 1.2.8
configure: checking neon library
checking for neon-config... /usr/local/bin/neon-config
checking neon library version... 0.25.5
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 recognise 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 f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... f95
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether f95 accepts -g... yes
checking the maximum length of command line arguments... 32768
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 -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
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for f95 option to produce PIC... -fPIC
checking if f95 PIC flag -fPIC works... yes
checking if f95 static flag -static works... yes
checking if f95 supports -c -o file.o... yes
checking whether the f95 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether libtool accepts --tag=XXX... yes
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 Mac OS KeyChain Services... 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 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... /usr/bin/ruby
checking for rb_hash_foreach()... yes
checking for rdoc... none
checking for Ruby major version... 1
checking for Ruby minor version... 8
checking for swig... /usr/bin/swig
checking swig version... 1.3.29
configure: Configuring python swig binding
checking for Python includes... -I/usr/include/python2.4
checking for compiling Python extensions... gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC
checking for linking Python extensions... gcc -pthread -shared
checking for linking Python libraries...
checking for apr_int64_t Python/C API format string... l
checking perl version... 5008008
configure: Configuring Ruby SWIG binding
checking for Ruby include path... -I. -I/usr/lib64/ruby/1.8/x86_64-linux
checking how to compile Ruby extensions... gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall  -fPIC $(SWIG_RB_INCLUDES)
checking how to link Ruby extensions... gcc -shrext .so -shared
checking where to install Ruby scripts... /usr/lib/ruby/site_ruby/1.8
checking where to install Ruby extensions... /usr/lib/ruby/site_ruby/usr/lib64/ruby/site_ruby/1.8/x86_64-linux
checking how to use output level for Ruby bindings tests... normal
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.pl
config.status: creating contrib/client-side/svncopy.pl
config.status: creating contrib/client-side/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.sleepycat.com/download/index.shtml

Then I run 'make', and here's the section that goes bad.

Code:

cd subversion/libsvn_subr && /bin/sh /root/subversion-1.4.5/libtool --tag=CC --silent --mode=link gcc  -g -O2  -g -O2 -pthread    -rpath /usr/local/subversion/lib -o libsvn_subr-1.la  auth.lo cmdline.lo compat.lo config.lo config_auth.lo config_file.lo config_win.lo constructors.lo ctype.lo date.lo dso.lo error.lo hash.lo io.lo kitchensink.lo lock.lo md5.lo nls.lo opt.lo path.lo pool.lo prompt.lo quoprint.lo simple_providers.lo sorts.lo ssl_client_cert_providers.lo ssl_client_cert_pw_providers.lo ssl_server_trust_providers.lo stream.lo subst.lo svn_base64.lo svn_string.lo target.lo time.lo user.lo username_providers.lo utf.lo utf_validate.lo validate.lo version.lo xml.lo /usr/local/apache2/lib/libaprutil-1.la -lsqlite3 -lexpat /usr/local/apache2/lib/libapr-1.la -luuid -lrt -lcrypt  -lpthread -ldl -lz
/usr/lib/libexpat.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make: *** [subversion/libsvn_subr/libsvn_subr-1.la] Error 1

And I'm pretty lost at this point. SO any type of direction or help would be useful.

Charlie

neocontrol 11-06-2007 11:07 AM

On another note,

My end goal is to have SVN+https.

I can't use any of the mod_dav_svn stuff for some reason, whereby just dong the loadmodule in httpd.conf. I'm really running out of options here other than just going down to doing this all thru ssh+svn.


All times are GMT -5. The time now is 02:51 AM.