Can't compile KDE programs

[Vincent]

I've just installed Fedora Core 2 for the first time on a new AMD 64 3000+ system. Unfortunately, I can't compile KDE applications although I've installed the KDE development packages. I guess the libraries are installed in /usr/lib64/kde3.

When I run a configure script it quits with the error "in the prefix you've chosen, there are no KDE libraries installed" even when I use configure --prefix=/usr/lib64/kde3

Running kde-config --prefix gives the response /usr.

Can anyone help me?
Thanks in advance.

Best wishes,
Vincent

[foolish]

Check that the packages really are installed:

rpm -qa | grep kde

[triplehead]

i can reproduce same error, this is output from kaffeine xine based player after ./configure

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for kde-config... /usr/bin/kde-config
checking where to install... /usr (as returned by kde-config)
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
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
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether g++ supports -Wmissing-format-attribute... yes
checking whether gcc supports -Wmissing-format-attribute... yes
checking whether g++ supports -Wundef... yes
checking whether g++ supports -Wno-long-long... yes
checking whether g++ supports -Wnon-virtual-dtor... yes
checking whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fno-common... yes
checking whether g++ supports -fexceptions... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -O0... yes
checking whether g++ supports -Wl,--no-undefined... yes
checking whether g++ supports -Wl,--allow-shlib-undefined... yes
not using lib directory suffix
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
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 whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
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 for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... 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 ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
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 -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
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 for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
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 whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for shl_load... (cached) no
checking for shl_load in -ldld... (cached) no
checking for dlopen... (cached) no
checking for dlopen in -ldl... (cached) yes
checking whether a program can dlopen itself... (cached) yes
checking whether a statically linked program can dlopen itself... (cached) yes
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for g77 option to produce PIC... -fPIC
checking if g77 PIC flag -fPIC works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking if C++ programs can be compiled... yes
checking for strlcat... no
checking if strlcat needs custom prototype... yes - in libkdefakes
checking for strlcpy... no
checking if strlcpy needs custom prototype... yes - in libkdefakes
checking for main in -lutil... yes
checking for main in -lcompat... no
checking for crypt in -lcrypt... yes
checking for socklen_t... 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 sys/types.h... (cached) yes
checking for stdint.h... (cached) yes
checking sys/bitypes.h usability... yes
checking sys/bitypes.h presence... yes
checking for sys/bitypes.h... 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 if res_init needs -lresolv... yes
checking if res_init is available... yes
checking for killpg in -lucb... no
checking for int... yes
checking size of int... 4
checking for short... yes
checking size of short... 2
checking for long... yes
checking size of long... 8
checking for char *... yes
checking size of char *... 8
checking for dlopen in -ldl... (cached) yes
checking for shl_unload in -ldld... no
checking for size_t... yes
checking size of size_t... 8
checking for unsigned long... yes
checking size of unsigned long... 8
checking sizeof size_t == sizeof unsigned long... 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 vsnprintf... yes
checking for snprintf... yes
checking for X... libraries /usr/X11R6/lib64, headers /usr/X11R6/include
checking for IceConnectionNumber in -lICE... yes
checking for libXext... yes
checking for pthread_create in -lpthread... yes
checking for extra includes... no
checking for extra libs... no
checking for libz... -lz
checking for libpng... -lpng -lz -lm
checking for libjpeg6b... no
checking for libjpeg... -ljpeg
checking for perl... /usr/bin/perl
checking for Qt... libraries /usr/lib64/qt-3.3/lib, headers /usr/lib64/qt-3.3/include using -mt
checking for moc... /usr/lib64/qt-3.3/bin/moc
checking for uic... /usr/lib64/qt-3.3/bin/uic
checking whether uic supports -L ... yes
checking whether uic supports -nounload ... yes
checking if Qt needs -ljpeg... no
checking for rpath... yes
checking for KDE...
configure: error:
in the prefix, you've chosen, are no KDE libraries installed. This will fail.
So, check this please and use another prefix!

everything else ok but the last two lines errors

[Vincent]

Yes, triplehead that is exactly what happens here. Not only with kaffeine, but also with kile, kmplayer, ... At least we share a problem :)

After several installations and Googles, I still can't compile KDE packages :(

It seems to me that the packages are installed. Running rpm -qa | grep kde gives a list of kde packages, including kdelibs and several -devel packages. The configure script has no problem finding the Qt libraries in /usr/lib64/

Using an explicit --prefix to /usr/lib64/ or /usr/lib64/kde3 or creating a symbolic link in
/usr/lib to /usr/lib64/kde3 all doesn't work.

Apparently compiling programs isn't supported on the AMD64 :(
Best wishes,
Vincent

[triplehead]

Yes, triplehead that is exactly what happens here. Not only with kaffeine, but also with kile, kmplayer, ... At least we share a problem :)

After several installations and Googles, I still can't compile KDE packages :(

It seems to me that the packages are installed. Running rpm -qa | grep kde gives a list of kde packages, including kdelibs and several -devel packages. The configure script has no problem finding the Qt libraries in /usr/lib64/

Using an explicit --prefix to /usr/lib64/ or /usr/lib64/kde3 or creating a symbolic link in
/usr/lib to /usr/lib64/kde3 all doesn't work. :D

Apparently compiling programs isn't supported on the AMD64 :(
Best wishes,
Vincent

it's KDE problem, i have compiled mplayer, xmms and others with no errors :) :)

[danfunk]

Try this:

/configure --enable-libsuffix=64

[foolish]

Make sure you have all the -devel files needed. Like kdelib-devel

[rbk]

I found a fix for this bug on a dual-Opteron FC2-64 system. I got the same output from ./configure, trying to build Kile from sources (and, yes, I definitely have all the ***-devel packages installed).

The solution is (1) use danfunk's suggestion "./configure --enable-libsuffix=64", BUT... (2) go to /usr/lib64/qt-3.3 and do "ln -s lib lib64" to create a symlink from /usr/lib64/qt-3.3/lib to /usr/lib64/qt-3.3/lib64.

The initial problem is that ./configure doesn't know to look in /usr/lib64 for KDE and QT. When you tell it to use the "64" suffix, it rather stupidly changes every instance of "lib" to "lib64"... as a result, it proceeds to look for QT's internal libraries in /usr/lib64/qt-3.3/lib64. QT, of course, doesn't know or care where it's been installed, so it still uses "lib"... thus the fix.

The real fix for this would be to make configure more intelligent... but until somebody does that (and hell freezes over), this seems a fairly harmless hack.

Cheers,
RBK

[zg0000]

To get some kde-look styles to install I had to use:

./configure --enable-libsuffix=64 --with-qt-dir=/usr/lib64/qt-3.3/ -with-qt-libraries=/usr/lib64/qt-3.3/lib/

Otherwise I was getting a qt-mt error (I think thats what it said anyway).

After running:

yum install kdebase-devel kdegraphics-devel kdelibs-devel

of course.

[Adaptive]

I am having trouble compiling kmymoney because configure cannot find the KDE dir. I have tried, where --prefix is supposed to be my KDE dir

./configure --enable-libsuffix=64 --with-qt-dir=$QTDIR --prefix=/usr
./configure --enable-libsuffix=64 --with-qt-dir=$QTDIR --prefix=/usr/lib64/kde3
./configure --with-qt-dir=$QTDIR --prefix=/usr
./configure --with-qt-dir=$QTDIR --prefix=/usr/lib64/kde3

the qt libraries are found fine, but in all cases I get the error:
checking for KDE... configure: error:
in the prefix, you've chosen, are no KDE libraries installed. This will fail.
So, check this please and use another prefix!

Also, I am sure that all of the the kde stuff is installed.

[root@hemt kmymoney2-0.6.2]# rpm -qa | grep kde
kdegraphics-3.2.2-1
kdeartwork-3.2.2-1
kdemultimedia-3.2.2-2
kdegames-3.2.2-1
kdeaddons-3.2.2-1
kdeutils-devel-3.2.2-3
kdelibs-devel-3.2.2-8.FC2
kdepim-3.2.2-2
kdeadmin-3.2.2-2
kdenetwork-devel-3.2.2-1
kdelibs-3.2.2-8.FC2
lockdev-1.0.1-2.3.1
lockdev-devel-1.0.1-2.3.1
kdeutils-3.2.2-3
kdesdk-3.2.2-2
kdesdk-devel-3.2.2-2
kdegraphics-devel-3.2.2-1
kdenetwork-3.2.2-1
kdepim-devel-3.2.2-2
kdebase-3.2.2-6.FC2
kdebase-devel-3.2.2-6.FC2
kdevelop-3.0.3-1

Can someone help me please?

[joshua197]

Having just installed FC4 x86-64 and updated KDE to 3.5, I found exactly the problem described by Vincent when trying to compile the standard KDE 'Hello' program.

I do have all of the devel files installed (in /usr/lib64/kde).

I take it this problem hasn't been fixed in FC4 then?

Sorry, to wake everyone up in a thread that's been sleeping since October 2004, but as a relative newb, I find it frustrating that something as basic as this hasn't been fixed.

Should I remove Kdevelop and then reinstall from the source rpm, telling the installation process where to find the lib files?