./configure errors still

Longman, Bill yellowdog-newbie@lists.terrasoftsolutions.com
Mon, 29 Sep 2003 16:04:50 -0700


> I need to find out what I need to install so I can run 
> ./configure.  I have 
> placed the output below of the error that I am getting.  The 
> error is way at 
> the bottom, but I wanted to send the whole thing in case some 
> on may be able 
> to see some thing that I am missing.  I am sure I just need 
> to download some 
> thing to make this work, but not sure what.

<snip>
Okay, here it's found your C compiler....

> 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 how to run the C preprocessor... gcc -E

Now it's looking for a C++ compiler....

> checking for g++... no
> checking for c++... no
> checking for gpp... no
> checking for aCC... no
> checking for CC... no
> checking for cxx... no
> checking for cc++... no
> checking for cl... no
> checking for FCC... no
> checking for KCC... no
> checking for RCC... no
> checking for xlC_r... no
> checking for xlC... no
> checking whether we are using the GNU C++ compiler... no
> checking whether g++ accepts -g... no
> checking dependency style of g++... none
> checking whether g++ supports -Wundef... no
> checking whether g++ supports -Wno-long-long... no
> checking whether g++ supports -Wnon-virtual-dtor... no
> checking how to run the C++ preprocessor... /lib/cpp
> checking whether g++ supports -frepo... no
> checking whether g++ supports -instances=explicit... no
> not using lib directory suffix

Now it's looking for libraries....

> 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...
> checking whether ln -s works... yes
> checking how to recognise dependant libraries... pass_all
> checking for egrep... grep -E

And now it's looking for header declarations....

> 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 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 ranlib... ranlib
> checking for strip... strip
> checking if gcc static flag  works... no
> 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/bin/ld) supports shared 
> libraries... yes
> checking whether -lc should be explicitly linked in... no
> 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... no
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking whether the g++ linker (/usr/bin/ld) supports shared 
> libraries... yes
> libtool.m4: error: problem compiling C++ test program
> checking for g++ option to produce PIC...
> checking if g++ supports -c -o file.o... no
> checking whether the g++ 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
> appending configuration tag "GCJ" to libtool
> checking if gcj supports -fno-rtti -fno-exceptions... (cached) no
> checking for gcj option to produce PIC... -fPIC
> checking if gcj PIC flag -fPIC works... no
> checking if gcj supports -c -o file.o... no
> checking whether the gcj linker (/usr/bin/ld) supports shared 
> libraries... no
> 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 for msgfmt... /usr/bin/msgfmt
> checking for gmsgfmt... /usr/bin/msgfmt
> checking for xgettext... /usr/bin/xgettext
> checking for main in -lutil... yes
> checking for main in -lcompat... no
> checking for crypt in -lcrypt... yes
> checking for socklen_t... size_t
> checking for dnet_ntoa in -ldnet... no
> checking for dnet_ntoa in -ldnet_stub... no
> checking for inet_ntoa... yes
> checking for connect... yes
> checking for remove... yes
> checking for shmat... yes
> checking crt_externs.h usability... no
> checking crt_externs.h presence... no
> checking for crt_externs.h... no
> checking for _NSGetEnviron... no
> checking for sys/types.h... (cached) yes
> checking for stdint.h... (cached) yes
> checking for poll in -lpoll... no
> checking CoreAudio/CoreAudio.h usability... no
> checking CoreAudio/CoreAudio.h presence... no
> checking for CoreAudio/CoreAudio.h... no
> checking for res_init... no
> checking if res_init needs custom prototype... res_init unavailable
> checking for killpg in -lucb... no
> checking for int... yes
> checking size of int... 4
> checking for long... yes
> checking size of long... 4
> checking for char *... yes
> checking size of char *... 4
> checking for char... yes
> checking size of char... 1
> checking for dlopen in -ldl... yes
> checking for shl_unload in -ldld... no
> checking for vsnprintf... yes
> checking for snprintf... yes

Looking for X libraries and headers now....OOF!

> checking for X... configure: error: Can't find X includes. 
> Please check your 
> installation and add the correct paths!
> [root@localhost khacc-1.7.1]#

You need XFree86-devel and you may as well also get gcc-c++ and
libstdc++-devel. It's noticing no C++ compiler.

Finally, you shouldn't need to compile as root. Compile the code as your own
login, and just use root to do the install.