kdevelop 0.4 on SuSE 6.1 - configure problems

[Pahan, Szabolcs]

>Heiko Nardmann wrote:
>> 
>> Hi!
>> 
>> I have tried to install kdevelop 0.4 on my SuSE 6.1 system.
>> After unpacking the tar.gz file I have done the following:
>> 
>> ./configure --prefix=/usr/opt/kdevelop-0.4 --enable-static
>> --enable-shared
>> 
>> Both shared and static libraries shall be built and the whole thing
>> shall
>> be installed under /usr/opt/kdevelop-0.4.
>> 
>> The configure run results in the following output:
>> 
>> loading cache ./config.cache
>> checking for extra includes... no
>> checking for extra libs... no
>> configure: warning: 
>***************************************************
>> configure: warning: ---KDevelop is alpha!. It may not even 
>compile.---
>> configure: warning: -------------Use at your own 
>risk-----------------
>> configure: warning: 
>***************************************************
>> checking for a BSD compatible install... /usr/bin/ginstall -c
>> checking whether build environment is sane... yes
>> checking whether make sets ${MAKE}... 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 for a C-Compiler...
>> 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 how to run the C preprocessor... gcc -E
>> checking for a C++-Compiler...
>> checking for g++... g++
>> checking whether the C++ compiler (g++  -s) works... yes
>> checking whether the C++ compiler (g++  -s) is a cross-compiler... no
>> checking whether we are using GNU C++... yes
>> checking how to run the C++ preprocessor... g++ -E
>> checking for flex... flex
>> checking for flex... (cached) flex
>> checking for yywrap in -lfl... yes
>> checking lex output file root... lex.yy
>> checking whether yytext is a pointer... yes
>> checking host system type... i686-pc-linux-gnu
>> checking build system type... i686-pc-linux-gnu
>> checking for ranlib... ranlib
>> checking for ld used by GCC... /usr/i486-linux/bin/ld
>> checking if the linker (/usr/i486-linux/bin/ld) is GNU ld... yes
>> checking for BSD-compatible nm... /usr/bin/nm -B
>> checking command to parse /usr/bin/nm -B output... yes
>> checking for _ prefix in compiled symbols... (cached) no
>> checking whether ln -s works... yes
>> checking for object suffix... o
>> 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 if g++ supports -c -o file.lo... yes
>> checking if g++ supports -fno-rtti -fno-exceptions ... yes
>> checking if g++ static flag -static works... -static
>> checking if the linker (/usr/i486-linux/bin/ld) is GNU ld... yes
>> checking whether the linker (/usr/i486-linux/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/i486-linux/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... no
>> checking whether to build static libraries... yes
>> checking for objdir... .libs
>> checking for dlopen... no
>> checking for dlopen in -ldl... no
>> checking for dld_link in -ldld... no
>> checking for shl_load... no
>> checking for shl_load in -ldld... no
>> creating libtool
>> checking whether NLS is requested... yes
>> checking for msgfmt... /usr/bin/msgfmt
>> checking for gmsgfmt... /usr/bin/msgfmt
>> checking for xgettext... /usr/bin/xgettext
>> checking for libz... -lz
>> checking for X... libraries /usr/X11R6/lib, headers 
>/usr/X11R6/include
>> checking for libpng... -lpng -lz -lm
>> checking for main in -lcompat... no
>> checking for main in -lcrypt... yes
>> checking for the third argument of getsockname... socklen_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 for killpg in -lucb... no
>> checking for Qt... configure: error: Qt (>= 1.42 and < 2.0) 
>(libraries)
>> not found. Please check your installation!
>> 
>> Two things have to be mentioned here:
>> 1) Although I said that shared libraries have to be built 
>the check says
>> that no shared
>>    libraries should be built.
>>    I "fixed" this by modifying the configure file.
>> 2) The error in finding the Qt installation. Here is the 
>config.log file
>> saying what has gone
>>    wrong here:
>> 
>> This file contains any messages produced by compilers while
>> running configure, to aid debugging if configure makes a mistake.
>> 
>
>ad 2) where are the QT lib/includes installed ? Is the QTDIR set
>properly ?

I think the problem is still the good old one: 
qtcompat.rpm 
package has not been installed.

Szabczy