Bug 458866

Summary: kdvelop hangs on libtool
Product: [openSUSE] openSUSE 11.1 Reporter: S. P. <rob.bob.301>
Component: DevelopmentAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: forgotten_kHYb7eJGnH, grey-olli, ifmmasvwama, pth, sysop
Version: Final   
Target Milestone: ---   
Hardware: All   
OS: openSUSE 11.1   
Whiteboard:
Found By: Community User Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description S. P. 2008-12-12 22:12:23 UTC
Observed in openSUSE 11.1 RC1 64-bit.
Processor: AMD Athlon single core. 4GB RAM.

To reproduce: 
1. Create the simplest C++ project (auto-generated)
2. Click build project.
3. The process hangs on libtool
4. Then, it seems to be generating endless error report.

Note: libtool was added using a separate installation step
via Yast -> Software -> software management -> search "libtool"
Comment 1 S. P. 2008-12-12 22:38:26 UTC
I just checked out my c++ project I have been developing using Suse 11.0
I cannot build my project in OpenSUSE 11.1 RC 1 -- the symptoms are
exactly the same as in the case of an auto-generated simple c++ project.
Comment 2 Norbert Meyer 2009-01-02 02:52:47 UTC
I had this problem too.
Problem: 
libtool (shell-script) is generated by configure.
configure is generated by aclocal, autoheader, ...

libtool defines a variable 
ECHO="echo"
but uses a variable 
$echo

The variable echo is empty. This empty variable produce the crash.
see also ltmain.sh - search for '\$echo'

simple workaround:
Add a line 
echo="echo"
after the line 
ECHO="echo"
in libtool (do not replace the line!).
This should solve the problem (until the next run of configure). 

better workaround:
change the file /usr/share/aclocal/libtool.m4 (be root!)
Save the file first!
- search for "_LT_PROC_ECHO_BACKSLASH" (without "")
- add the line 
echo=${lt_ECHO-echo}
after the line 
ECHO=${lt_ECHO-echo}
You can also add a modified version of the test follows this line.
- add the line 
_LT_DECL([], [echo], [1], [An echo program that does not interpret backslashes])
near the end of the macro after the line 
_LT_DECL([], [ECHO], [1], [An echo program that does not interpret backslashes])
- run automake etc., configure -> the generated libtool should contain the line
ECHO="echo"
and the line
echo="echo"

Comment 3 S. P. 2009-01-16 22:26:13 UTC
Thank you for the workaround. It remedied the issue.
Here is the diff of my changes to /usr/share/aclocal/libtool.m4

1069d1068
< echo=${lt_ECHO-echo}
1208,1209d1206
<     [An echo program that does not interpret backslashes])
< _LT_DECL([], [echo], [1],
Comment 4 Matthias Hopf 2009-01-17 15:07:53 UTC
I think the diff is created the wrong way (think you have to add those lines). Also, as a suggestion, diff -u creates easier readable diffs.

Looks like a duplicate of bug 455882. Or the other way round.
Comment 5 S. P. 2009-01-19 05:17:55 UTC
Thank you for pointing out the diff direction.
I believe you are right about bug 455882.
Comment 6 Matthias Hopf 2009-01-20 11:46:19 UTC
Development is severely hindered by a broken libtool.
Raising priority therefore.
Comment 7 Matthias Hopf 2009-01-29 11:16:34 UTC
Run 'libtoolize' (invoked by autoreconf, invoked typically by ./autogen.sh). That copies a new libtool into the build directory that's compatible with the installed aclocal files.

Of course this doesn't explain why kdevelop creates a wrong version by default.
Comment 8 Andreas Schwab 2009-02-11 10:36:16 UTC
You can't mix and match macros from different libtool versions.
Comment 9 Philipp Thomas 2009-03-02 17:32:54 UTC
To #7: I guess kdevelop uses outdated libtool macros/files. If using libtoolize solves the problem, it's a kdevelop bug and needs to be assigned to the kdevelop maintainer(s).
Comment 10 Michael McCarthy 2009-03-24 14:55:33 UTC
Why is this marked invalid???  It is an issue with they way kdevelop works that needs to be addressed.
Comment 11 Olli Artemjev 2009-05-05 23:43:22 UTC
https://bugzilla.novell.com/show_bug.cgi?id=461703 may correlate to this?
Comment 12 Forgotten User kHYb7eJGnH 2010-01-15 09:33:11 UTC
As per comment 4 and comment 5

*** This bug has been marked as a duplicate of bug 455882 ***