[Bug 58999] debugger will not start

[Alexandros Karypidis]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=58999     




------- Additional Comments From karypid at inf.uth.gr  2003-08-06 11:23 -------
Hi, 
 
The exact same thing happens here (running CVS of 05/08/2003 on SuSE 8.2). 
 
I have noticed that /usr/bin/libtool claims to be version 1.4.3 whereas libtool 
in my project directory said it was 1.4.1. 
 
Simply updating libtool in the project directory by copying /usr/bin/libtool 
makes the debugger start, so I suppose this is the only file that affects this. 
 
I then did "make clean" and "make distclean" to make libtool disappear and ran 
"./configure" again to have a new one generated. 1.4.1 popped up again and the 
problem reappears: 
 
./libtool --version 
ltmain.sh (GNU libtool) 1.4.1 (1.922.2.34 2001/09/03 01:22:13) 
 
This is interesting as I have 1.4.3 installed: 
 
> rpm -qa | grep libtool 
libtool-1.4.3-43 
> /usr/bin/libtool --version 
ltmain.sh (GNU libtool) 1.4.3 (1.922.2.111 2002/10/23 02:54:36) 
 
I am no auto-tools expert, but it seems that the problem is: 
 
- KDevelop 3 requires libtool 1.4.3 
- I have libtool 1.4.3 installed: 
- A KDevelop project's libtool is generated by ./configure 
- Autoconf generates a ./configure which generates libtool 1.4.1 
 
So, the issue here is to have autoconf generate a ./configure which generates a 
1.4.3 libtool. 
 
Cheers!