You probably want to be sending mails like this to users@ in the
future, not dev@, since it's a problem specific to your build.
Looking at your configure output, you're linking to apr 0.9 and
apr-util 1.2. This is bad, since 0.x and 1.x are binary-incompatible.
Your --with-apr and --with-apr-util arguments needs to point to the
same versions, preferable 1.2 both. Point these variables to
apr-config and apu-config binaries, respectively, rather than
directories.
On 3/11/07, Meryl Silverburgh <silverburgh.meryl@gmail.com> wrote:
> Hi,
> I download and compile subversion on RHEL4.
>
> I run the '.configure' with this value ' ./configure
> --with-apr=/usr/local/apr --with-apr-util=/usr/local/apr'
>
> after I 'make' and 'make install',
> these commands work "svn --version" "svn --help"
>
> But when I try 'svnserve -d', I get a 'Segmentation fault'
> # svnserve -d
> Segmentation fault
>
> Any idea why this is happening?
> Here is the full output of the configure command :
>
> # ./configure --with-apr=/usr/local/apr --with-apr-util=/usr/local/apr
> configure: Configuring Subversion 1.4.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 ANSI C... 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 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... 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... 0.9.12
> 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... no
>
> An appropriate version of neon could not be found, so libsvn_ra_dav
> will not be built. If you want to build libsvn_ra_dav, please either
> install neon 0.25.5 on this system
>
> or
>
> get neon 0.25.5 from:
> http://www.webdav.org/neon/neon-0.25.5.tar.gz
> unpack the archive using tar/gunzip and rename the resulting
> directory from ./neon-0.25.5/ to ./neon/
>
> no suitable neon found
> 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... g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g77 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) 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
> 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 g77 option to produce PIC... -fPIC
> checking if g77 PIC flag -fPIC works... yes
> checking if g77 static flag -static works... yes
> checking if g77 supports -c -o file.o... yes
> checking whether the g77 linker (/usr/bin/ld) 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()... no
> configure: WARNING: The detected Ruby is too old for Subversion to use
> configure: WARNING: A Ruby which has rb_hash_foreach is required to use the
> configure: WARNING: Subversion Ruby bindings
> configure: WARNING: Upgrade to the official 1.8.2 release, or later
> checking for swig... /usr/local/bin/swig
> checking swig version... 1.3.31
> configure: WARNING: Detected SWIG version 1.3.31
> configure: WARNING: Subversion requires 1.3.24 or later, and is known to work
> configure: WARNING: with versions up to 1.3.29
> configure: Configuring python swig binding
> checking for Python includes... -I/usr/include/python2.3
> checking for compiling Python extensions... gcc -pthread
> -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m32 -march=i386
> -mtune=pentium4 -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... 5008005
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 11 22:04:02 2007