[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Libtool 2.2.2 to 2.2.4 fails configure in KDevelop
From: |
Daedalus |
Subject: |
Libtool 2.2.2 to 2.2.4 fails configure in KDevelop |
Date: |
Tue, 27 May 2008 18:02:43 +0200 |
User-agent: |
Thunderbird 2.0.0.14 (X11/20080522) |
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.
- Libtool 2.2.2 to 2.2.4 fails configure in KDevelop,
Daedalus <=