Version: 1.7.1 (using KDE KDE 3.3.1) Installed from: RedHat RPMs Compiler: gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3) OS: Linux I downloaded the Fedora Core 3 SRPM from kile's sourceforge page (I'm using FC3 x86_64 and was getting random crashes with the i386 version). When attempting to build the SRPM, I got the following error from some configure scripts: checking if UIC has KDE plugins available... configure: error: not found - you need to install kdelibs first. kdelibs is, of course installed. I solved the problem by searching in the ./configure script contained in both .tar.bz2 files for the word "klineedit" and replacing with "KLineEdit". The configure script search in actest.cpp file (generated by uic for the test) has the wrong QT class for the KLineEdit plugin. Apparently this is a very common problem with many different programs...
By the way, that having all been said...I now have a x86_64 build of Kile for FC3. If you guys would like it for distribution, let me know. Thanks, Jeff
Sure that this is not a problem of this specific .src.rpm?
Maybe, but it's the official FC3 .src.rpm from the kile web site. Also, from my searching on the web when attempting to fix this problem, I found that the "klineedit" vs. "KLineEdit" thing is a common problem with many software packages, not just kile. Either way, I think it's worth fixing it in this .src.rpm.
This bugreport applies only to an old version of kile and had no comments since one year. Therefore I close it. Thanks Thomas Braun
I'm reopening this because there's no information as to whether this was ever fixed. There were no new comments because I presumed someone was going to fix it at some point, but I never heard about it again. Did anyone ever go and fix the lines in the configure script? If not, and you guys want it to be fixed, I have commit access to the KDE SVN now and I'll be happy to go do a search + replace. Don't want to step on toes though.
Hello, actually we don't want it fixed. Version 1.7 is way too old to be used anymore. Everyone should run the latest greatest :)
Okay. But did you fix this error in 1.9.2's configure script? :-)