Version: 0.9pre (using KDE 3.1.9) Compiler: gcc version 3.3.1 20030626 (Debian prerelease) OS: Linux (i686) release 2.4.21 The configure script could need some additional checks. I am not sure what it checks but is should check for: all kde packages including dev files libfam-dev if required Because the users from resent mails had problems with files from this package.
KDE releases only source packages. If you're talking about pre-compiled binary packages, you have to talk to your distribution's packagers. We're not responsible for their packages.
I am talking about the configure script of boson, which is not a kde cvs application. It is hostet on sf ;) The problem is that our configure script doesn't check some things. Like the existing of some files from kde-dev packages and if that packages where compiled with fam support and if libfam.la is there.
We also need to write our own OpenGL checking code - KDE's checks aren't sufficient anymore for our needs. See e.g. http://www.linuxforen.de/forums/showthread.php?s=29946e7d166df3fd37d9a566a8541582&threadid=76048 (german!) We should 1. search for libGL.so -> if not found: complain about missing libGL.so (NOT just "OpenGL missing") and ask to install OpenGL drivers (e.g. nvidias proprietary drivers, x11 drivers, ...) 2. search for GL/gl.h -> if not found: complain about missing GL/gl.h and ask to install OpenGL headers (iirc nvidias drivers should do that on installation) 3. search for libGLU.so -> if not found: complain about missing libGLU.so and ask to install GLU. Usually this is in a package named mesa-glu or similar (nvidia or other drivers do _not_ include GLU) 4. search for GL/glu.h -> if not found: complain about missing GLU headers and ask to install them. Usually in mesa-glu-devel or similar. And of course the "kdelibs-devel depends on libfam-devel, but RPM is too stupid to notice" problem is an important one, too. Anyone knows how to find this out? Maybe we can do ldd libkdecore.so | grep libfam ? Better: libtool is trying to add libfam.a on linking. Find out how libtool knows that it needs to do so and emulate that behaviour in the configure script. CU Andi
I guess this has been fixed, since we don't use autotools anymore. CU Andi