FS#10173 - [kdevelop] libtool-2.2-2 fails configure
Attached to Project:
Arch Linux
Opened by Patrik Lindström (patson) - Saturday, 12 April 2008, 18:53 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 23 October 2009, 05:22 GMT
Opened by Patrik Lindström (patson) - Saturday, 12 April 2008, 18:53 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 23 October 2009, 05:22 GMT
|
Details
Description:
I have a KDevelop/autotools project, which uses libtool. Libtool 2.2-2 seems to report false information to the configure script, which leads to the linker going into an infinite fork() loop during linking of the final binary. Using version 1.5.26-1 on sources configured using 2.2-2 also causes the fork loop; a distclean followed by a reconfigure using the older version makes linking work again (with both 1.5.26-1 and 2.2-2). Using KDevelop 3.5.1, autoconf 2.61, automake 1.10.1 Steps to reproduce: Start new autotools based C++ project in KDevelop, attempt configure/compile using libtool 2.2-2, observe failure. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Friday, 23 October 2009, 05:22 GMT
Reason for closing: None
Additional comments about closing: kdevelop 3.5 is no more in [extra]
Friday, 23 October 2009, 05:22 GMT
Reason for closing: None
Additional comments about closing: kdevelop 3.5 is no more in [extra]
I tried it with a C project and a C++ project but I got always the same result: after about 30 seconds the CPU goes mad and the only option I have to recover the system is to unplug the power connector.
I'm attaching the two samples of code I used for the test and their respective build output (obviusly before the crash).
However, last time I managed to kill the Kdevelop window using the CTRL+ALT+ESC combination but this dind't change the situation: the system was still slow and almost unresponsive.
What test do you want me to do next? And ehhr...do you know a method to recover the system responsiveness without unplugging the power cord?(CTRL+ALT+CANC after about 15 minutes didn't reboot/shutdown the system)
If you want to compile the project follow these steps:
1. Click on Compile->Compile Project;
2. When in the bottom log windows it says "linking [projectname] (libtool)" click Compile->Interrupt
3. Go to the \debug directory in your project root
4. Remove libtool
5. Create a simlynk to /usr/lib/libtool using the command "ln -s /usr/bin/libtool libtool"
6. Click again on Compile->Compile Project
7. Everything should work now, until you clean or dist-clean your project
Now...anyone knows how to fix autotools or at least how to automate the process?
What are you referring to? What should I do?
What does "report it upstream" mean? Sorry for my ignorance.
read the section about reporting bugs. they seem to not have a bugtracker but a bug mailing list. so report it there and give us here a link to your post in the mailing list archive so we can follow where it goes.
If they give me some kind of link or information about the bug I will
let you know.
But I can't understand what to do lol.
that when the compilation starts if I check the ltmain.sh in the project root it says "Version 1.5a" (which it seems to be bad).
How to solve this thing definitely? Shall we contact the KDevelop team?
http://bugs.kde.org/show_bug.cgi?id=163915 here they say that it's solved in the last kdevelop svn but I didn't try since I moved to Eclipse.
It works for me :)