Version: 3.0.3 (using KDE KDE 3.2.2) Installed from: Unlisted Binary Package Compiler: gcc 3.3.3 OS: Linux I downloaded kdevelop-3.0.3.tar.bz2. Untarred it in my home directory (/home/andy), no problems. Went into the kdevelop-3.0.3 directory and typed "./configure" . Config starts and goes fine until it gets to "Looking for Qt... ". The whole system then locks up. (I know this because clock stops in lower-right of screen). Waited for 20 min - no change. This bug sounds quite similar to bug 20839. I am using Mepis Linux, version 2004.05. KDE version 3.2.2 .
Reproducible? Do you have a stable system?
Hi Stephen - thanks for this (and my apologies for posting to the bug-list as a non-member ( I got an email that mentioned that ) . Yes, I've just managed to reproduce the bug about 5 min ago (very easily!). Same as before - I get the message "checking for Qt ... " and the whole system locks up. I'm using Mepis Linux version 2004.5, and using the 2.6.4 kernel ( it allows you to choose between that and the 2.4 kernel). Just wondering - as a relative newcomer to Linux - should I have d/loaded the bz2 file to "/" and untarred it there (instead of in /home/andy ) ? Just thought I'd check ... :-) Is my system stable? Yes, very much so (apart from this, and I'm kinda surprised that it's possible to lock up the 2.6.4 kernel ! .. ;-) Anyway - very happy with Mepis. Hope this may help. I'm *very willing* to send you the CD if that will help (now that I've installed Mepis, I don't really need it!) . Bye for now - - Andy On Wednesday 19 May 2004 03:57 pm, Stephan Binner wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=81789 > binner kde org changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Severity|crash |normal > > > > ------- Additional Comments From binner kde org 2004-05-19 21:57 ------- > Reproducible? Do you have a stable system?
Not a KDevelop problem per se. No one else seems to have this problem and the Qt check is generic and probably part of every KDE program's build settings. Closing as INVALID.