Hi
I am trying to install Kdevelop. When I run the ./conifure command, it ends saying with the following lines: "checking for KDE. . . cinfigure:error: in the prefix you have chosen, are no KDE headers installed. This will fail"

What does this mean and how can I fix it?

Eric

Do you have KDE installed and running? KDevelop needs KDE to run.

Yea I am running KDE 1.1.2!

Try using 'locate kapp.h' to find where the headers are installed. In particular, you are concerned with the location of the KDE 'include' directory.

Example:

/foo/bar/include/kapp.h

then you should set the KDEDIR environment in the 'configure' file to the top KDE dir (this is /foo/bar in this example)

After editing that and saving it, try './configure' again.

ok I gave it a shot. I ran 'locate kapp.h' at the terminal as root, and it did nothing but put me back at root?
Help!

Try running 'updatedb' first. That will update the Database that locate looks into to find files. (run these as root of course)

If, after running 'updatedb', you still can not find the file then it is not installed on your system. Are you running Redhat? We will have to find which package provides that file and install it

Running updateb says "command not found"

I am running Best Linux "the latest version"

as root, and in the '/' directory, type:

find / | grep kapp.h

or

find / | grep updatedb

so you can then use 'updatedb' and then

'locate kapp.h'

ok I did exactly what you have suggested and now I get the following: find: /proc/6/fd: Permission Denied


Lol
I dont know what to do any suggestions!


Eric

Okay.. it looks like Best Linux is really built on top of Redhat. I don't know what changes they have made but at least it uses RPMS so that helps.

It looks like kapp.h is an essential part of KDE and I am curious as to how you have KDE installed and working without having it on your system. Maybe its just part of the KDE Development package.

1st question? Why are you compiling this instead of using the RPM?

If you use the RPM package manager, it will tell you what packages are missing that it depends on. For example:

My system is running Redhat 7.0. I don't have KDE or KDevelop installed. If I try to install kdevelop, I get:

[root@CXO336745-x86-RH7 RPMS]# rpm -Uvh kdevelop-1.2-12.i386.rpm
error: failed dependencies:
kdesupport-devel is needed by kdevelop-1.2-12
kdelibs-devel is needed by kdevelop-1.2-12
libjscript.so.2 is needed by kdevelop-1.2-12
libkdecore.so.2 is needed by kdevelop-1.2-12
libkdeui.so.2 is needed by kdevelop-1.2-12
libkfile.so.2 is needed by kdevelop-1.2-12
libkfm.so.2 is needed by kdevelop-1.2-12
libkhtmlw.so.2 is needed by kdevelop-1.2-12
libkimgio.so.2 is needed by kdevelop-1.2-12
libqt.so.1 is needed by kdevelop-1.2-12
[root@CXO336745-x86-RH7 RPMS]#

so.. the first two lines are listings of packages that are dependencies for KDevelop. The rest of the lines are some specific files that are probably in those first two packages. Got it?

Okay now, here is the deal. That RPM I was trying to install is a binary that is compiled for my specific distribution. It may or may not work on Best Linux even though Best Linux is pretty much built on Redhat. I don't see a Kdevelop RPM on the Best Linux site. You can try getting the one from ftp.redhat.com ( and the dependent packages ) or... you can try to find a SRC.RPM

As luck would have it, if you go to ftp://ftp.sonic.net/pub/linux/kde/kdevelop
There are SRC.RPM's for Redhat. You can get those and then do the following:

rpm --rebuild some_rpm_name.SRC.RPM

That will recompile the RPM and put it in the /usr/src/redhat/RPMS directory or somewhere like that. Just look at the last few lines when its done and it will say something like "Leaving /usr/src/redhat/RPMS" and thats where it will be. Then you can issue:

rpm -Uvh some_rpm_name.RPM

from that directory, as root, and it will either install or fail and tell you why.


SO.. here is what I would do:

FIrst try getting the kdevelop and dependent packages from ftp.redhat.com
See if those work. If not.. go to that other site and get the .SRC.RPMs and then rebuild them and see if they work.
(If you poke around on Redhat they might have SRC rpms too)