On 2/25/06, C. Brouerius van Nidek
On Friday 24 February 2006 06:17, Shriramana Sharma wrote:
Thursday, 23 February 2006 22:15 samaye, Jerry Feldman alekhiit:
The problem here is that the OP's tarball is probably not a valid package. It is probably a source tarball where one needs to manually untar the archive, configure, make and make install.
Some tarballs are not properly recognized by the GUI -- see my recent post on "Is there a bug with Ark". Try to decompress the tgz by using tar xvzf <filename> on the command line.
Done the decompressing in /home and I read the README. According to the README I should install the package with ./configure then make and as root makeinstall.
Started out with ./configure and after a long row of activities I get following information at the end:
checking for rpath... yes 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!
No idea if and when which prefix I have chosen. What is meant with this sentence and how to proceed?
Normally, all required headers are installed with KDE. Invoking "kde-config --prefix" should return the basepath (prefix) of the KDE installation (i.e. /opt/kde3). If no prefix is specified "/usr/local" is used by default. You may combine the call to kde-config and configure: # ./configure --prefix=`kde-config --prefix` It should now find the headers successfully write a config file. \Steve