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.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Thanks for your response. I don't think this has anything to do with rpms, as I am compiling the source files. I understand what you mean about libraries, maybe this is a PATH problem.
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).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
