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
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

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]
Comment by Travis Willard (Cerebral) - Friday, 09 May 2008, 19:19 GMT
does the libtool from testing fix this?
Comment by Travis Willard (Cerebral) - Saturday, 10 May 2008, 12:32 GMT
PS - to try the testing version of libtool, enable [testing] in /etc/pacman.conf and run pacman -Sy libtool
Comment by Ippazio Martella (pazioman) - Sunday, 11 May 2008, 10:17 GMT
I got the same problem. I tried the testing version but no luck.
Comment by Andreas Radke (AndyRTR) - Monday, 12 May 2008, 10:36 GMT
please test libtool 2.2.4-1 from testing and autoconf 2.62 from core.
Comment by Ippazio Martella (pazioman) - Monday, 12 May 2008, 16:11 GMT
I tried with libtool 2.2.4-1 from testing but it still doesn't work.
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).
Comment by Ippazio Martella (pazioman) - Monday, 12 May 2008, 16:17 GMT
Sorry, I clicked the wrong button lol.

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)
Comment by Andreas Radke (AndyRTR) - Monday, 12 May 2008, 16:42 GMT
this seems to be a kdevelop issue. http://bugs.kde.org/query.cgi - please check for existing bug reports or file a new one and give us the url.
Comment by Travis Willard (Cerebral) - Monday, 12 May 2008, 17:00 GMT
http://bugs.kde.org/show_bug.cgi?id=142727 <-- they closed it as invalid, seems they think it's an autotools problem
Comment by Ippazio Martella (pazioman) - Monday, 12 May 2008, 18:10 GMT
Confirmed. It's an autotools problem.
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?
Comment by Andreas Radke (AndyRTR) - Sunday, 25 May 2008, 22:00 GMT
please report it upstream and give us the url here to follow it
Comment by Ippazio Martella (pazioman) - Monday, 26 May 2008, 17:32 GMT
Sorry Andreas I'm a complete noob about signaling bugs and so on.
What are you referring to? What should I do?
What does "report it upstream" mean? Sorry for my ignorance.
Comment by Andreas Radke (AndyRTR) - Monday, 26 May 2008, 18:39 GMT
http://www.gnu.org/software/libtool/#bug

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.
Comment by Ippazio Martella (pazioman) - Tuesday, 27 May 2008, 16:05 GMT
I sent an email to bug-libtool@gnu.org.
If they give me some kind of link or information about the bug I will
let you know.
Comment by Andreas Radke (AndyRTR) - Wednesday, 28 May 2008, 05:23 GMT Comment by Andreas Radke (AndyRTR) - Wednesday, 28 May 2008, 10:19 GMT Comment by Ippazio Martella (pazioman) - Wednesday, 04 June 2008, 17:53 GMT
It seems the Autotools team has solved the issue and it speaks about it here : http://lists.gnu.org/archive/html/bug-libtool/2008-05/msg00086.html.
But I can't understand what to do lol.
Comment by Ippazio Martella (pazioman) - Wednesday, 04 June 2008, 18:04 GMT
So, I tried to replace /opt/kde/share/apps/kapptemplate/admin/ltmain.sh with /usr/share/libtool/config/ltmain.sh but I noticed
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?
Comment by Andreas Radke (AndyRTR) - Wednesday, 11 June 2008, 21:54 GMT
ask to reopen the kde bugreport or create a new one and point to the answer you got on the libtool list. the kdevelop template script seems to be outdated and conflicts with new autotools. they should update it.
Comment by Ippazio Martella (pazioman) - Thursday, 12 June 2008, 14:38 GMT
The link in KDevelop board is here: http://bugs.kde.org/show_bug.cgi?id=163915.
Comment by Andreas Radke (AndyRTR) - Wednesday, 25 June 2008, 04:57 GMT
http://bugs.kde.org/show_bug.cgi?id=142727 - we will have to wait for a solution.
Comment by Ippazio Martella (pazioman) - Thursday, 26 June 2008, 18:47 GMT
It's a bit upsetting they didn't give me a final workaround or something like that. I mean: We know it's a problem with the obsolete lsmain.sh generated by KDevelop (KDev programmers say it's automake fault because they broke backward compatibility, automake guys say it's Kdev fault because they don't fix things BAH!) .In fact if I replace the old ltmain.sh with the new one from the libtool folder the compilation works. I tried to replace every single ltmain.sh contained in the tarballs in /share/apps/kdevappwizard/ but once again KDevelop uses the old ltmain.sh. Is there a way to track what files KDevelop opens and discover where is the original bugged ltmain.sh??
Comment by Jud (judfilm) - Friday, 05 December 2008, 08:40 GMT
Is this still a problem?
Comment by Ippazio Martella (pazioman) - Friday, 05 December 2008, 18:46 GMT
Yes the problem is still there but it doesn't seem to be ArchLinux related.
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.
Comment by Andreas Radke (AndyRTR) - Friday, 12 December 2008, 21:37 GMT
last release 3.5.3 doesn't have the fix acording to the fixes list. it's even not listed in the unreleased 3.5.4 fixes list. the 4.x release will still take a while. there's currently no Arch developer responsible for kdevelope. i'm about to close this as "upstream issue". i'll also ask on the dev list if somebody wants to take it.
Comment by Andrea Scarpino (BaSh) - Saturday, 10 January 2009, 02:32 GMT
I updated 3.5.4 on testing, please try the new version
Comment by Luka Borkovic (fLuXx) - Sunday, 11 January 2009, 02:01 GMT
Tried the new version, but the problem persists. Using libtool 2.2.6a.
Comment by dAdE (dadesito) - Wednesday, 25 February 2009, 00:45 GMT Comment by Roman Kyrylych (Romashka) - Saturday, 13 June 2009, 09:42 GMT
is this still an issue with 3.9.93-1 from testing?
Comment by Andreas Radke (AndyRTR) - Sunday, 09 August 2009, 13:53 GMT
libtool is Allan's pkg for a while. removing myself and assign it to Allan.
Comment by Allan McRae (Allan) - Sunday, 09 August 2009, 14:07 GMT
And it is clearly not a libtool bug. It is caused by kdevelop shipping a ltmain.sh script that is incompatible with the libtool.m4 file provided by libtool. The workaround is given in the link given by dAdE above.

Loading...