Development

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • Issues building SVN..

    0 answers - 6566 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    the weekend I installed MySQL on my Fedora Core 3 box. This was
    installed via yum which apparently upgraded a bunch of other items, Python
    being one of them and now I'm getting all sorts of errors, in fact yum no
    longer works but that's another story (I think).
    In the process, my installation of Subversion as busted. I'm not sure what
    the issue is.
    I have snagged the latest source and when I try to run: ./configure
    -without-berkley-db -with-apr=/usr/local/apr it errors out attempting to do
    something with the Java bindings (it appears).
    The full output is attached.
    Can anyone tell me what the problem is. I was not able to find anything
    online to help me out.
    configure: Configuring Subversion 1.3.0
    checking build system type i686-pc-linux-gnu
    checking host system type i686-pc-linux-gnu
    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 for egrep grep -E
    checking whether ln -s works yes
    configure: Apache Portable Runtime (APR) library configuration
    checking for APR yes
    checking APR version 0.9.6
    configure: Apache Portable Runtime Utility (APRUTIL) library configuration
    checking for APR-util yes
    checking APR-UTIL version 0.9.6
    configuring libtool now
    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 for a sed that does not truncate output /bin/sed
    checking how to recognise dependent libraries pass_all
    checking command to parse /usr/bin/nm -B output ok
    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
    checking dlfcn.h usability yes
    checking dlfcn.h presence yes
    checking for dlfcn.h yes
    checking for ranlib ranlib
    checking for strip strip
    checking for objdir .libs
    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 if gcc supports -c -o file.lo yes
    checking if gcc supports -fno-rtti -fno-exceptions no
    checking whether the linker (/usr/bin/ld) supports shared libraries yes
    checking how to hardcode library paths into programs immediate
    checking whether stripping libraries is possible yes
    checking dynamic linker characteristics GNU/Linux ld.so
    checking if libtool supports shared libraries yes
    checking whether to build shared libraries yes
    checking whether to build static libraries yes
    checking whether -lc should be explicitly linked in no
    creating libtool
    checking whether libtool accepts libtool: unrecognized option
    `'
    Try `libtool ' for more information.
    no
    checking whether libtool needs -no-undefined no
    configure: checking neon library
    checking for neon-config /usr/local/bin/neon-config
    checking neon library version 0.24.7
    checking for static Apache module support no
    checking for Apache module support via DS through APXS found at
    /usr/sbin/apxs
    checking httpd version recent enough
    checking for socket in -lsocket no
    checking for availability of Berkeley DB yes
    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 for python2 /usr/bin/python2
    checking that the Python found is at least version 2.0 yes
    checking for JDK configure: WARNING: no JNI header files found.
    no
    checking for perl /usr/bin/perl
    checking for ruby /usr/local/bin/ruby
    checking for rb_hash_foreach() yes
    checking for swig /usr/local/bin/swig
    checking swig version 1.3.24
    checking for swig library directory /usr/local/share/swig/1.3.24
    configure: Configuring python swig binding
    checking if swig needs -L for its libraries -L/usr/local/share/swig
    checking for Python includes -I/usr/include/python2.4
    checking for compiling Python extensions gcc -pthread
    -fno-strict-aliasing -DNDEBUG -g -pipe -Wp,-D_FRTIFY_SURCE=2
    -fexceptions -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables
    -D_GNU_SURCE -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 5008006
    configure: Configuring Ruby SWIG binding
    checking for Ruby include path -I.
    checking how to compile Ruby extensions gcc -g $(SWIG_RB_INCLUDES)
    checking how to link Ruby extensions gcc -shrext .so -shared
    checking where to install Ruby scripts /
    checking where to install Ruby extensions
    /
    checking for makeinfo echo cannot run makeinfo
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating svn-config
    config.status: creating tools/backup/hot-backup.py
    config.status: creating
    config.status: creating contrib/client-side/svncopy.pl
    config.status: creating
    config.status: creating
    config.status: creating
    config.status: creating
    config.status: creating
    config.status: creating
    config.status: is unchanged
    config.status: executing mkdir-init commands
    mkdir
    : bad interpreter: No such file or directorysh: /bin/sh
    mkdir
    : bad interpreter: No such file or directorysh: /bin/sh
    Thanks!
    Kyle Heon
    kheon (AT) comcast (DOT) net

Re: Issues building SVN..


max 4000 letters.
Your nickname that display:
In order to stop the spam: 4 + 3 =
QUESTION ON "Development"

EMSDN.COM