PDA

View Full Version : checking for X



muertala
06-12-2002, 07:51 AM
Now I have a problem when I do ./configure it goes thru its normal process of checking stuff but when it get to
checking for X ....... include not found
then it stops. Anyone got any suggestions on what I may be missing


Now I just found Cryonics reply to a similar question. His response was to read:

http://seq.sourceforge.net/showthre...s=&threadid=273

Now this is the Guide I guess I should specify is error above a result of a missing package and if so what package may I be missing. Here is where it stops.


./configure
loading cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... (cached) /usr/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... found
checking whether to enable maintainer-specific portions of Makefiles... no
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 c++... (cached) 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++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for working const... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... (cached) yes
checking whether make sets ${MAKE}... (cached) yes
checking for ranlib... (cached) ranlib
checking for ld used by GCC... (cached) /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking for object suffix... o
checking for executable suffix... 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 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 (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... 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 for objdir... .libs
creating libtool
loading cache ./config.cache
checking for extra includes... no
checking for extra libs... no
checking for libz... -lz
checking for X... include not found

high_jeeves
06-12-2002, 08:33 AM
Please follow the walkthrough. You are missing the X development packages.

--Jeeves

muertala
06-12-2002, 08:56 AM
Are you talking about these packages:

gd-1.8.4-4.i386.rpm
gd-devel-1.8.4-4.i386.rpm
gdbm-1.8.0-10.i386.rpm
gdbm-devel-1.8.0-10.i386.rpm

Ratt
06-12-2002, 09:10 AM
No, those are the database packages.

muertala
06-12-2002, 09:27 AM
Ok so which ones are the X development packages.

S_B_R
06-12-2002, 09:56 AM
They're the ones you dont have... :rolleyes: follow the walk through and see what packages are required that you don't have..
rpm -qa | more

HINT: look for the packages with "X" in the name..... ...