#1 config script problem?

v1.0 (example)
open
nobody
5
2002-06-25
2002-06-25
Anonymous
No

Any time I use --with-xercesc the build fails.

The environment is solaris8 sparc,
(280r,UltraII,ultra60).

xerces Version c1.7.0
(GNU Autoconf) 2.53
GNU Make version 3.76.1
cc-5.0

# ./configure --enable-aif --enable-ag_tcl
--enable-tcl-pkgdir --enable-ag_python
--enable-python-pkgdir --enable-bigball
--with-xercesc=/usr/local/xerces-c1_7_0
--with-tcl=/usr/local/tcltk-8.4.1a/lib
--with-python=/usr/local/python-2.2/bin/python
checking for a BSD-compatible install...
/usr/local/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for gcc... no
checking for cc... cc
checking for C compiler default output... 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... no
checking whether cc accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of cc... none
checking for g++... g++
checking whether we are using the GNU C++ compiler...
yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether make sets ${MAKE}... (cached) yes
checking for ranlib... ranlib
checking build system type... sparc-sun-solaris2.8
checking host system type... sparc-sun-solaris2.8
checking for non-GNU ld... /usr/ccs/bin/ld
checking if the linker (/usr/ccs/bin/ld) is GNU ld...
no
checking for /usr/ccs/bin/ld option to reload object
files... -r
checking for BSD-compatible nm... /usr/xpg4/bin/nm -p
checking whether ln -s works... yes
checking how to recognise dependant libraries...
pass_all
checking command to parse /usr/xpg4/bin/nm -p output...
ok
checking how to run the C preprocessor... cc -E
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... no
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... (cached) ranlib
checking for strip... strip
checking for objdir... .libs
checking for cc option to produce PIC... -KPIC
checking if cc PIC flag -KPIC works... yes
checking if cc static flag -Bstatic works... yes
checking if cc supports -c -o file.o... yes
checking if cc supports -c -o file.lo... no
checking whether the linker (/usr/ccs/bin/ld) supports
shared libraries... yes
checking how to hardcode library paths into programs...
immediate
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... solaris2.8
ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
creating libtool
checking "xercesc library"... hmm..you seem to have
libxerces-c1_7_0
checking libxerces-c1_7_0... no
configure: error: xercesc library needed to complete
building

Regards,

Chris

Christopher D. Frazee
Systems Administrator
Sony Electroncs

Phone:(408) 955-4696
3300 Zanker Road MS#sj1b5
San Jose, Ca. 95134

Chris@slt.sel.sony.com

Discussion

  • Logged In: NO

    Please note that I have tried using prebuilt binaries (from
    the apache web site) as well as compiled my own with gcc as
    well as cc, and still get the same error. Just to make
    sure, I have gone through my /usr/local/bin, /usr/local/lib
    /usr/local/sbin, /usr/local/include, and created symbolic
    lings to all of the files under my xerceces build, to make
    sure there were no rogue binaries floating around, and I
    still have problems. Please note also that I have tried
    using explicit --with-xercesc-include= and
    --with-xercesc-lib=, and I still have the same problem.

     
  • Steven Bird
    Steven Bird
    2002-06-25

    • priority: 5 --> 7
    • assigned_to: nobody --> xma
     
  • Steven Bird
    Steven Bird
    2002-06-25

    • assigned_to: xma --> haepal
    • labels: 325269 --> 436157
     
  • Xiaoyi Ma
    Xiaoyi Ma
    2002-06-25

    • priority: 7 --> 5
    • labels: 436157 --> Install Problem (example)
    • assigned_to: haepal --> nobody
     
  • Xiaoyi Ma
    Xiaoyi Ma
    2002-06-25

    Logged In: YES
    user_id=197371

    Chris,

    The configure script works with GCC. It looks like the
    configure script
    picks cc over gcc, this might be the reason for the failure.

    > checking for gcc... no
    > checking for cc... cc
    ...
    > checking for g++... g++
    > checking whether we are using the GNU C++ compiler...
    yes

    Please put gcc on your PATH, or

    if using csh,tcsh

    setenv CC <path of your gcc>

    if using bash:

    export CC=<path of your gcc>

    Then run configure again. Hope this will fix the problem.

    Please let me know how it works out.

     
  • Haejoong Lee
    Haejoong Lee
    2002-06-25

    Logged In: YES
    user_id=135609

    There could be many reasons. Would you please upload
    "config.log" file that was created when you configured the
    source? It helps to narrow down the cause of the failure.

     
  • Logged In: NO

    The configure script works with GCC. It looks like the
    configure script
    picks cc over gcc, this might be the reason for the failure.

    > checking for gcc... no
    > checking for cc... cc
    ...
    > checking for g++... g++
    > checking whether we are using the GNU C++ compiler... yes

    Please put gcc on your PATH, or

    if using csh,tcsh

    setenv CC <path of your gcc>

    if using bash:

    export CC=<path of your gcc>

    ####################

    Actually this appears to be a issue with the script finding
    the appropriate
    libraries for linking problem not a compiler issue, from
    what I can tell.
    However I did as you requested, and as I expected it still
    failed. . .

    Here are the logs that are relevant. One set is from with
    cc, and the other is
    with gcc.

    -Chris