Re: Libtool 2.2.2 to 2.2.4 fails configure in KDevelop

[Ralf Wildenhues]

Hello,

* Daedalus wrote on Tue, May 27, 2008 at 06:02:43PM CEST:
> I think I found a bug in libtool/autotools. I'm using these softwares:
> - Arch Linux with kernel 2.6.25
> - KDevelop 3.5.1
> - automake 1.10.1
> - autoconf 2.62
> - libtool 2.2.4
>
> 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).
> The KDevelop staff closed a ticket  
> (http://bugs.kde.org/show_bug.cgi?id=142727)about this issue
> claiming it's an autotools problem.
>
> STEPS TO REPRODUCE:
> Start a new autotools based C or C++ project in KDevelop, then try to  
> compile/configure. The system should
> fail during the linking process.

I'm having trouble in reproducing this on my system.  Maybe it's easy
for you to show us the bug: please try the supposedly-looping command
manually in the project directory.  If it still hangs or loops, please
try adding --debug to see what it does.  Post what you find, but pack
and/or cut off voluminous output at some sensible point, please.

Also, I see that the bug has been reported over a year ago.  That means,
it likely isn't new with Libtool version 2.2, if it is indeed an
autotools bug at all.

It's a bit disappointing that the bug has not been forwarded at that
time, if only to clarify whether it's really autotools rather than
Kdevelop which is at fault here.

Thanks for the bug report now,
Ralf