bug-libtool
[Top][All Lists]
Advanced

[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: Tue, 27 May 2008 22:21:17 +0300
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080329 SeaMonkey/1.1.9

Daedalus wrote:
Hi,
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.

WORKAROUND (found on http://bugs.kde.org/show_bug.cgi?id=142727):
1. Start the compile process
2. Cancel the operation when it starts the linking phase
3. Remove the libtool script (generated by configure) from the /debug directory in the project root
4. Create a link to /usr/bin/libtool
5. Restart the compile process again

I hope this would help you to track down and fix this annoying bug. Good work.

Could you confirm that libtool scrip is generated from libtool 2.2.4.
What is value of VERSION in ltmain.sh script ?

Roumen




reply via email to

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