Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I tried compiling vim on RH WS3 and it compiles ok (vim6.3) but even though I
used ./configure --enable -gui=auto (or even motif)
it doesn't compile with gui support.
The configure output says GUI - no support
rpm -q openmotif says it is installed.
So I tried compiling kvim using
./configure --enable-gui=kde --with-qt-dir=/usr/lib/qt-3.1/lib
and I get the same type of result.
Does anyone who has done this before have a suggestion as to what I could be doing wrong?
If you're looking to build a program against some library you will need the "devel" package corresponding to the library's package in order to build it. The devel packages contain headers and other files you will need in order to build something that uses that package. kde-<version>-devel and qt-<version>-devel might be the names, but I'm not the person to ask since I'm not that used to rpm based systems.
Well, in order to compile the source you still need to have the headers. The fact that you have a library installed doesn't mean you have the header files (from the -devel package) which are needed to compile software that use that library.
When you compile stuff that depends on a library the source will have include lines in the code. These will tell the compiler to look for header files to get information about library functionality (etc) from. These include files come with the devel packages.
That doesn't make any sense. The vim sources are shipped in one big tarball or several smaller ones. The GTK/GTK2 GUI support known as "gvim" is enabled by passing the appropriate parameters to the configure script (i.e. ./configure --enable-gtk2-check).