Bug 163915

Summary:	Libtool 2.2.2 to 2.2.4 fails configure
Product:	[Applications] kdevelop	Reporter:	Martella Ippazio <daedalushack>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	3.5.1
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Martella Ippazio 2008-06-12 16:37:49 UTC

Version:           3.5.1 (using KDE 3.5.9)
Installed from:    Compiled From Sources
Compiler:          gcc 4.3.0 
OS:                Linux

Issue:
When I try to compile a simple C or C++ project using autotools, everything works fine until
KDevelop starts the linking process using libtool. Linking never ends and libtool make my
system unresponsive because it occupies all the resources (an infinite loop I suppose).

This bug has been already discussed here http://bugs.kde.org/show_bug.cgi?id=142727, but in the
end someone deduced that it's probably a autotools problem.

Well, after discussing the issue in the ArchLinux board (http://bugs.archlinux.org/task/10173) and
in the Autotools board(http://lists.gnu.org/archive/html/bug-libtool/2008-05/msg00063.html), the
autotools devs said it's a KDevelop problem!(http://lists.gnu.org/archive/html/bug-libtool/2008-05/msg00086.html)

The issue seems to be provoked by an obsolete configure script ($KDEDIR/share/apps/kapptemplate/admin/ltmain.sh).
Any patch? I tried to replace the original ltmain.sh from the KDE dir with the one in the libtool folder, but
whenever I start a new project the old ltmain.sh is still used :\. (Yeah it seems pretty impossible but that's it)

Comment 1 Amilcar do Carmo Lucas 2008-06-12 16:50:13 UTC

Did you really compiled KDevelop from sources ?
If yes, why didn't you use KDevelop 3.5.2 ?
If not, where did you get the packages ?

The packages provided at kdevelop.org should not suffer from that problem (I hope).

The autotools stuff that KDevelop uses comes from KDE, so this might be a KDE issue.

On incorrectly packaged KDevelop it might be a packager problem. SuSE for instance messes this up.

Comment 2 Andreas Pakulat 2008-06-12 19:15:37 UTC

Its not a kdevelop issue, if anything its an issue with KDE's admin/ directory and you should've re-opened the old bugreport. I'm closing this one as duplicate, will re-open the old issue and re-assign to the buildsystem component. But don't expect a fix, nobody is really working on KDE3 anymore, especially not on the completely broken buildsystem.

Still IMHO the issue is with litool, it shouldn't break so horribly on older scripts. Also 2.2.x seems pretty new, maybe the need to iron out some bugs still :)

Besides that: You replaced the wrong ltmain.sh, KDevelop keeps its templates in tar.gz's in share/apps/kdevappwizard/

*** This bug has been marked as a duplicate of 142727 ***

Comment 3 Amilcar do Carmo Lucas 2008-06-27 13:26:35 UTC

There have been commits (post 3.5.2) to KDevelop in SVN that might fix this issue.
Please update and retest.