PDA

View Full Version : Error during ./configure



BikerJon
09-02-2004, 01:36 AM
Here is the entire output from ./configure. I am running SuSE 9.1 with a complete installation of all packages.

linux:/showeq # ./configure
checking build system type... i686-suse-linux
checking host system type... i686-suse-linux
checking target system type... i686-suse-linux
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/showeq/missing: Unknown `--run' option
Try `/showeq/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for g++... g++
checking for supported compiler version... checking for style of include used by make... GNU
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 g++ accepts -g... yes
checking dependency style of g++... gcc3
yes
checking for gcc... gcc
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 dependency style of gcc... gcc3
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for an ANSI C-conforming const... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/i586-suse-linux/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 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 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... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
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 static flag works... yes
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 supports -c -o file.o... yes
checking whether the gcc linker (/usr/i586-suse-linux/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/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i586-suse-linux/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++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i586-suse-linux/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 stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for supported libc version... yes
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for IceConnectionNumber in -lICE... yes
checking for libXext... yes
checking for extra includes... no
checking for extra libs... no
checking for libz... -lz
checking for libpng... -lpng -lz -lm
checking for Qt... yes
>> Found version.: 3.3.1
>>> Headers......: /usr/lib/qt3/include/
>>>> Libraries...: /usr/lib/qt3/lib/
>>>>> Workable...: -*{ YES }*-
checking for Qt MOC... yes
checking if Qt compiles without flags... no
checking for pthread_create in -lpthread... yes
setting Linux pthread compilation options
checking for pcap_open_live in -lpcap... yes
checking for gdImageCreate in -lgd... no
checking for gdImagePng in -lgd... no
checking for inflate in -lz... yes
checking for gdbm_open in -lgdbm... no
configure: error: cannot find gdbm library functions. Make sure libgdbm is installed

I searched my installation and found these files in /usr/lib/

lrwxrwxrwx 1 root root 23 2004-09-01 12:38 libgdbm_compat.so.3 -> libgdbm_compat.so.3.0.0
-rwxr-xr-x 1 root root 10091 2004-04-05 16:22 libgdbm_compat.so.3.0.0
lrwxrwxrwx 1 root root 16 2004-09-01 12:48 libgdbm.so.2 -> libgdbm.so.2.0.0
-rwxr-xr-x 1 root root 26620 2002-10-08 09:49 libgdbm.so.2.0.0
lrwxrwxrwx 1 root root 16 2004-09-01 12:38 libgdbm.so.3 -> libgdbm.so.3.0.0
-rwxr-xr-x 1 root root 23208 2004-04-05 16:22 libgdbm.so.3.0.0
lrwxrwxrwx 1 root root 14 2004-09-01 12:49 libgd.so.2 -> libgd.so.2.0.0
-rwxr-xr-x 1 root root 234036 2004-04-05 19:46 libgd.so.2.0.0

It appears to me that I have the libgdbm files necessary, but the ./configure command does not know their location. I have no more thoughts on how to fix my problem, and I would appreciate any help offered.

purple
09-02-2004, 05:40 AM
Have the header files too? I'm not a package user, but those fancy namby pamby package managers break up packages into normal and development versions a lot. Maybe you have the normal gdbm which will give you the libs but not the development version which will give you the headers thus allowing you to compile? Maybe find / -name gdbm.h and some patience will help.

Or check out your config.log if you really think you have all packages installed as you say in your post. It has the compiler calls made during configure and you can see where it can't find gdbm.h yourself or where the linker can't load -lgdbm.

A working test from config.log for example:
configure:11505: checking for gdbm_open in -lgdbm
configure:11536: g++ -o conftest -g -O2 conftest.cc -lgdbm -lz -lpcap >&5
configure:11539: $? = 0
configure:11542: test -s conftest
configure:11545: $? = 0
configure:11557: result: yes

It'll probably show you the source for conftest.cpp if it fails.