Check that the libexpat.so or whatever its called is in one of the
directorys
specified in /etc/ld.so.conf
if not then add the directory and run
ldconfig
----- Original Message -----
From: Gabe Bauman <[EMAIL PROTECTED]>
To: Sablotron Mailing List <[EMAIL PROTECTED]>
Sent: Thursday, June 21, 2001 6:37 PM
Subject: [Sab] Configure problems
I am currently attempting to build Sablot, but I can't get past the
configure script.
Here's the process...
$ configure
loading cache ./config.cache
checking for a BSD compatible install... (cached) /bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking for ranlib... (cached) ranlib
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for ld used by GCC... (cached) /boot/develop/tools/gnupro/bin/
ld
checking if the linker (/boot/develop/tools/gnupro/bin/ld) is GNU ld...
(cached) yes
checking for BSD-compatible nm... (cached) /boot/develop/tools/gnupro/
bin/nm -B
checking whether ln -s works... (cached) yes
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... none
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 ... yes
checking if gcc static flag -static works... -static
checking if the linker (/boot/develop/tools/gnupro/bin/ld) is GNU ld...
yes
checking whether the linker (/boot/develop/tools/gnupro/bin/ld)
supports shared libraries... yes
checking command to parse /boot/develop/tools/gnupro/bin/nm -B
output... ok
checking how to hardcode library paths into programs... immediate
checking for /boot/develop/tools/gnupro/bin/ld option to reload object
files... -r
checking dynamic linker characteristics... beos ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
loading cache ./config.cache
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... gcc -E
checking for c++... c++
checking whether the C++ compiler (c++ ) works... yes
checking whether the C++ compiler (c++ ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether c++ accepts -g... yes
checking how to run the C++ preprocessor... c++ -E
checking where to find xml parser... ./configure: 0: command not found
not found (panic)
configure: error: Couldn't find the expat libraries
$
=============
I have just done a straight install of the latest expat from
sourceforge, so it should be found. Is there an environment variable I
am missing here? Can I explicitly point the configure script at the
headers?
Gabe
