./configure (with nothing else) fails with the following error message:
******************************'
checking for KDE... configure: error:
in the prefix, you've chosen, are no KDE headers installed. This will fail.
So, check this please and use another prefix!
******************************

I seem to have lots of KDE files in /opt/kde3, and lots of headers in /opt/kde3/include. But running ./configure --prefix=/opt/kde3/ produces the exact same error message.

How can I find out the correct prefix?

Thank you for any advice!

It should work with that prefix. Weird.
Try this:

Code: Select all

./configure --prefix=/opt/kde3

Same as you mentioned but without the last slash.

Whether there is a slash at the end or not does not seem to matter.

I now put an echo line in the configure script and it looks like the prefix variable is /opt/kde3 even when I don't specify it on the command line. That is good, isn't it? However, where KDE includes are looked for, the kde_incdir variable is NO, instead of /opt/kde3/include, which is what one would expect.

Unfortunately, I'm not familiar with shell scripts.

Have you got the KDE headers installed (I think it's the 'kdebase-devel' package)? These are necessary for the SVN install.

Ermmm... I don't know whether the KDE headers are installed; neither do I know how to find out whether they are (I just know there is a largish number of .h files in /opt/kde3/include). I also don't know what SVN means; sorry.

Sakari wrote:Ermmm... I don't know whether the KDE headers are installed; neither do I know how to find out whether they are (I just know there is a largish number of .h files in /opt/kde3/include). I also don't know what SVN means; sorry.

SVN is the version control system we use to keep the sources. The SVN version just means the latest version of KT.

SUSE has some some sort of package manager (Yast ?), I guess, you can check there which packages are installed. Maybe somebody running SUSE can help us here.

Sakari wrote:Ermmm... I don't know whether the KDE headers are installed; neither do I know how to find out whether they are (I just know there is a largish number of .h files in /opt/kde3/include). I also don't know what SVN means; sorry.

Open YaST -> Software -> Software Management. This will open up the software management tool that lists all packages that are already installed or are available. There's several tools available from the dropdown menu in the top left to list software packages. Anyhow, the packages you need to install for sure are 'kdebase3-devel' and 'kdelibs3-devel'. There may be more, I'm not entirely sure, but the '-devel' packages contain the header files for the respective packages, so if the configure fails again, you may need other -devel packages as well.

Try that and see if it works.

djpearman wrote:Anyhow, the packages you need to install for sure are 'kdebase3-devel' and 'kdelibs3-devel'. There may be more, I'm not entirely sure, but the '-devel' packages contain the header files for the respective packages, so if the configure fails again, you may need other -devel packages as well.

Try that and see if it works.

Thank you; installing those two packages helped the configure script run succesfully. However, 'make' then fails with the message
***************************************************************
waitjob.cpp: In function `void bt::SynchronousWait(long unsigned int)':
waitjob.cpp:55: error: 'class KIO::NetAccess' has no member named '
synchronousRun'
make[3]: *** [waitjob.lo] Error 1
****************************************************************

This functionality has only been added in KDE 3.4, so you need at least this version of KDE.

George wrote:This functionality has only been added in KDE 3.4, so you need at least this version of KDE.

You can do this quite easily by adding internet repositories to your software sources in YaST and updating your entire system.