What I think is the problem here is that you don't have your X includes
i.e. Xlib.h etc header files in /usr/includeX11. If it's not so then do
made a proper link to whereever those are or just edit the 'configure'
script of your package(here KDevelop) to give the correct path of X
includes.
Good Luck,
Vivek


On Sat, 26 Aug 2000, Sukrit Mehra wrote:

> Date: Sat, 26 Aug 2000 11:03:36 +0530
> From: Sukrit Mehra <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED], [EMAIL PROTECTED],
     [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [LIH] KDevelop installation problem
> 
> I have been been trying to install K develop given with this months PCQ
> cd but I haven't been able to get through.
> First in the I give the command
> ./configure
> and this start a long process in which everything goes smoothly. But in
> the end the following message is given.
> 
> checking for shl_unload in -ldld...no
> checking for X...configure:error: can't find X includes. Please check
> your installation and add the correct paths!
> 
> CAn anyway please tell me how to go abou this installation.?
> 
> 
> 
> The complete log file for the installation is given below.
> _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:583: checking for extra includes
> configure:614: checking for extra libs
> configure:682: checking for a BSD compatible install
> configure:735: checking whether build environment is sane
> configure:792: checking whether make sets ${MAKE}
> configure:838: checking for working aclocal
> configure:851: checking for working autoconf
> configure:864: checking for working automake
> configure:877: checking for working autoheader
> configure:890: checking for working makeinfo
> configure:944: checking for a C-Compiler
> configure:950: checking for gcc
> configure:1056: checking whether the C compiler (gcc  ) works
> configure:1072: gcc -o conftest    conftest.c  1>&5
> configure:1098: checking whether the C compiler (gcc  ) is a
> cross-compiler
> configure:1103: checking whether we are using GNU C
> configure:1180: checking how to run the C preprocessor
> configure:1242: checking for a C++-Compiler
> configure:1248: checking for g++
> configure:1364: checking whether the C++ compiler (g++  -s) works
> configure:1380: g++ -o conftest   -s conftest.C  1>&5
> configure:1406: checking whether the C++ compiler (g++  -s) is a
> cross-compiler
> configure:1411: checking whether we are using GNU C++
> configure:1466: checking whether g++ supports -fno-exceptions
> configure:1498: checking whether g++ supports -fno-rtti
> configure:1530: checking whether g++ supports -fno-check-new
> configure:1643: checking whether g++ supports -fexceptions
> configure:1677: checking whether g++ supports -frtti
> configure:1715: checking how to run the C++ preprocessor
> configure:1814: checking whether g++ supports -frepo
> configure:1906: checking for Cygwin environment
> configure:1939: checking for mingw32 environment
> configure:1997: checking host system type
> configure:2018: checking build system type
> configure:2047: checking for ld used by GCC
> configure:2115: checking if the linker (/usr/bin/ld) is GNU ld
> configure:2132: checking for /usr/bin/ld option to reload object files
> configure:2144: checking for BSD-compatible nm
> configure:2180: checking whether ln -s works
> configure:2201: checking how to recognise dependant libraries
> configure:2311: checking for object suffix
> configure:2337: checking for executable suffix
> configure:2563: checking for ranlib
> configure:2630: checking for strip
> ltconfig:556:checking for g++ option to produce PIC
> ltconfig:686:checking that g++ PIC flag  -fPIC works.
> ltconfig:747: checking if g++ static flag -static works
> ltconfig:792: checking if g++ supports -c -o file.o
> ltconfig:793: g++ -c -O2 -fno-exceptions -fno-rtti -fno-check-new -frtti
> -o out/conftest2.o  conftest.c 1>&5
> ltconfig:825: checking if g++ supports -c -o file.lo
> ltconfig:826: g++ -c -O2 -fno-exceptions -fno-rtti -fno-check-new -frtti
> -c -o conftest.lo  conftest.c 1>&5
> ltconfig:877: checking if g++ supports -fno-rtti -fno-exceptions
> ltconfig:878: g++ -c -O2 -fno-exceptions -fno-rtti -fno-check-new -frtti
> -fno-rtti -fno-exceptions -c conftest.c  conftest.c 1>&5
> ltconfig:1860: checking if global_symbol_pipe works
> ltconfig:1861: g++ -c -O2 -fno-exceptions -fno-rtti -fno-check-new
> -frtti  conftest.c 1>&5
> ltconfig:1864: eval "/usr/bin/nm -B conftest.o | sed -n -e 's/^.*[
> ]\([ABCDGISTW]\)[       ][      ]*\(\)\([_A-Za-z][_A-Za-z0-9]*\)$/\1
> \2\3
> \3/p' > conftest.nm"
> ltconfig:1916: g++ -o conftest -O2 -fno-exceptions -fno-rtti
> -fno-check-new -frtti -fno-builtin -fno-rtti -fno-exceptions  -s
> conftest.c conftstm.o 1>&5
> ltconfig:2262: checking for dlfcn.h
> ltconfig:2300: checking whether a program can dlopen itself
> configure:2907: checking for flex
> configure:2940: checking for flex
> configure:2974: checking for yywrap in -lfl
> configure:2993: gcc -o conftest -O2  -s conftest.c -lfl   1>&5
> configure:3016: checking lex output file root
> configure:3037: checking whether yytext is a pointer
> configure:3056: gcc -o conftest -O2  -s conftest.c  -lfl 1>&5
> configure:3104: checking whether NLS is requested
> configure:3125: checking for msgfmt
> configure:3159: checking for gmsgfmt
> configure:3204: checking for xgettext
> configure:3251: checking for bool
> configure:3271: g++ -c -O2 -fno-exceptions -fno-rtti -fno-check-new
> -frtti  conftest.C 1>&5
> configure:3323: checking for libz
> configure:3349: gcc -o conftest -O2   -s conftest.c  -lz  1>&5
> configure:3379: checking for dlopen in -ldl
> configure:3423: checking for shl_unload in -ldld
> configure:3442: gcc -o conftest -O2  -s conftest.c -ldld   1>&5
> /usr/bin/ld: cannot find -ldld
> collect2: ld returned 1 exit status
> configure: failed program was:
> #line 3431 "configure"
> #include "confdefs.h"
> /* Override any gcc2 internal prototype to avoid an error.  */
> /* We use char because int might match the return type of a gcc2
>     builtin and then its argument prototype would still apply.  */
> char shl_unload();
> 
> int main() {
> shl_unload()
> ; return 0; }
> configure:3471: checking for X
> configure:3510: gcc -E  conftest.c >/dev/null 2>conftest.out
> configure:3506: X11/Intrinsic.h: No such file or directory
> configure: failed program was:
> #line 3505 "configure"
> #include "confdefs.h"
> #include <X11/Intrinsic.h>
> configure:3586: gcc -o conftest -O2  -s conftest.c -lXt  1>&5
> /usr/bin/ld: cannot find -lXt
> collect2: ld returned 1 exit status
> configure: failed program was:
> #line 3579 "configure"
> #include "confdefs.h"
> 
> int main() {
> XtMalloc()
> ; return 0; }
> 
> ----------------------------------------------
> An alpha version of a web based tool to manage
> your subscription with this mailing list is at
> http://lists.linux-india.org/cgi-bin/mj_wwwusr
> 


----------------------------------------------
Find out more about this and other Linux India 
mailing lists at http://lists.linux-india.org/

Reply via email to