[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Libtool 2.2.2 to 2.2.4 fails configure in KDevelop

From: Roumen Petrov
Subject: Re: Libtool 2.2.2 to 2.2.4 fails configure in KDevelop
Date: Fri, 30 May 2008 00:00:43 +0300
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20080329 SeaMonkey/1.1.9

Ralf Wildenhues wrote:

* 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.

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,

I'm able to reproduce. The report is with old ltmain.sh (version 1.5a).
This file is from kdevelop template directory ($KDEDIR/share/apps/kapptemplate/admin/ltmain.sh).

$ aclocal -I path_to_libtool_2.2x_macros
$ autoheader
$ automake
$ autoconf
$ ./configure
$ ./libtool --help -> hang
Note that libtoolize is not run.

But after:
$ cp path_to_libtool_2.2x_ltmain.sh .
$ ./configure
$ ./libtool --help -> OK
$ make -> SUCCESS

P.S. : the libtool scritp that hang is attached.

Attachment: libtool.gz
Description: application/gzip

reply via email to

[Prev in Thread] Current Thread [Next in Thread]