On Thursday 13 May 2004 21:59, Bob Pearson wrote:

Environment: SuSE Linux Pro 9.0 with core dumps enabled. AMD Athlon 1.1GB

I have updated to kde 3.2.2 from a SuSE mirror site (leo) and I am trying to build kmldonkey 0.10pre3 (http://www.kmldonkey.org/). I have successfully built it previously using kde 3.2.1. When running ./configure fr this program I get a core dump of /usr/lib/qt3/bin/uic caused by a SIGSEGV. It is trying to find out if qt designer plug-ins are available (they are).

I have tried to use YaST2 to find out what provides /usr/lib/qt3/bin/uic and a "rpm -q -a --provides /usr/lib/qt3/bin/uic" and "rpm -q -a --provides /usr/bin/uic" yields no output. Am I doing something wrong? Has anyone gotten kmldonkey 0.10pre3 build under kde3.2.2 and SuSE 9.0? What provides /usr/lib/qt3/bin/uic?

<snip> uic is a part of qt / qtdesigner. However I do not think your problems comes from there. I had a very similar problem and wasted many hours searching the problem there, only to eventually find it in the script template prepared by a certain kde version which then gets used by autoconf to build into the configure scripts. ------------------- Note: If your configure script does NOT contain "-impl actest.h" then all this does not apply to your problem ------------------- What I did find causing a segfault in uic when running configure is the inclusion of "-impl actest.h" in the configure script (this will get used when running uic by your configure script). This ("-impl actest.h") does only get included when the developer (the one running autoconf to build the configure script) has acquired incorrect templates for for acinclude.m4 or aclocal.m4 somewhere in /opt/kde. (which I noticed that an upgrade after they had been acquired unfortunaly did not overwrite with the corrected version). Let me repeat my earlier post (answer) "Re: [suse-kde] ./configure fehler: qt nicht gefunden (KDE 3.2.2)" here: I had similar compile errors, however not about "Qt with thread support", but about Qt in general. Depending on how the configure script of kmldonkey is build, this could be also what is causing your error. Have a look at this: The reason for the error I saw was that a certain version of kde's acinclude.m4 or aclocal.m4 (which the one who created the configure script for the app you try to compile probably got in an upgrade) does mess up the generation of the configure file. QUICK FIX: modify your configure script: =========================== 1) look for the line kde_line="$kde_line -impl actest.h actest.ui > actest.cpp" 2) take out: -impl actest.h the line should be now: kde_line="$kde_line actest.ui > actest.cpp" 3) look for "klineedit" and change it to "KLineEdit" The line should be: if test -f actest.cpp && grep KLineEdit actest.cpp > /dev/null; If you develop yourself, and get these errors in your configure scripts build in by autoconf, you need to clean the base scripts for acinclude.m4 or aclocal.m4 somewhere in /opt/kde. Autoconf takes these to build the files for teh app you develop, so once they are cleaned in /opt/kde the error does not get reintroduced when you rerun autoconf. HTH, Matt