"./configure" issue...

[N00B to Linux]

Hello all,

I am a new Linux user (atempting to configure a firewall atm, fun but kinda hard for a non Linux guy :p) and seen this program on a forum, so tried to test it.

Now, I am using MDK9.0 which appears to works quite fine but, here is what I got when trying ./configure :


# ./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... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal-1.4... found
checking for working autoconf... found
checking for working automake-1.4... found
checking for working autoheader... found
checking for working makeinfo... missing
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for g++... g++
checking for supported compiler version... yes
checking for gcc... 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... yes
checking whether gcc accepts -g... yes
checking for c++... g++
checking whether the C++ compiler (g++ ) works... yes
checking whether the C++ compiler (g++ ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether g++ accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for working 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 Cygwin environment... no
checking for mingw32 environment... no
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 how to recognise dependant libraries... pass_all
checking for object suffix... o
checking for executable suffix... no
checking command to parse /usr/bin/nm -B output... ok
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... no
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 whether the 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
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for supported libc version... yes
checking for extra includes... no
checking for extra libs... no
checking for libz... no
checking for X... no
configure: error: Can't find X includes. Please check your installation and add the correct paths!



I am quite sure someone will flame me, possible thing is that I deserve it. But after flames, can you just explain me WHY doesn't it find the path to my X ? Both KDE and Gnome installed.

Thanx

[high_jeeves]

Read the walkthrough (actually follow it, step by step, as well).. The problem here is that you decided that instead of following directions, you would just post a common problem to the boards. The second step (if reading isnt your strong point) would be to search, since I know this questions has been answered atleast 10 times on these boards...

Remember, lazy and stupid = bad.



you just explain me WHY doesn't it find the path to my X ? Both KDE and Gnome installed.


Well, atleast read the error message... does it say it cant find X? No.. read exactly what it says. As a side note: KDE and Gnome ARE NOT THE SAME THING as X.

--Jeeves

[Mr. Suspicious]

Hinting a bit more, it cannot find the "X includes".