By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1319

Summary: libtool: Version mismatch error.
Product: TDE Reporter: Nikolaus Klepp <office>
Component: tdesdkAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED FIXED    
Severity: blocker CC: bugwatch, darrella, kb9vqf, office
Priority: P5    
Version: R14.0.0 [Trinity]   
Hardware: i386   
OS: Debian Wheezy   
Compiler Version: TDE Version String:
Application Version: Application Name:

Description Nikolaus Klepp 2012-11-14 05:09:06 CST
When I create a new project in TDE from C++/TDE or C++/KDE the build fails with

libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2ubuntu1, but the
libtool: definition of this LT_INIT comes from libtool 2.4.2.
Comment 1 Timothy Pearson 2012-11-14 12:59:04 CST
I assume this is with kdevelop?
Comment 2 Nikolaus Klepp 2012-11-14 14:37:20 CST
kdevelop (from 3.5.13.1) + wheezy gives version mismatch error. 2.2.6b is from squeeze, which is not installed, 2.4.2 is from wheezy which is installed.

$ dpkg -S ltmain.sh
kapptemplate-trinity: /opt/trinity/share/apps/kapptemplate/admin/ltmain.sh
libtool: /usr/share/libtool/config/ltmain.sh

Shouldn't kdevelop use ltmain.sh from the installed libtool?


tdevelop (from R14.0.0, nightly builds) + wheezy gives the exact same error message.
Comment 3 Timothy Pearson 2012-11-14 14:58:08 CST
Yes it should; I just wanted to verify that kdevelop was indeed showing the problem before continuing.

This is an old bug inherited from KDE 3.5.10; it is conceptually relatively simple to fix if the following new steps are taken by kdevelop before building the application:
1.) Update the admin directory to the current GIT version tag for the installed TDE release.  Normally this would require Internet access, which is not desirable, therefore each kdevelop release should instead contain a copy of the correct admin directory GIT tree for deployment at build time.
2.) Copy the system's ltmain and libtool files to the admin directory.  The script to do this on Debian is:

	! [ -f /usr/share/libtool/ltmain.sh ] || \
	cp -f /usr/share/libtool/ltmain.sh admin/ltmain.sh
	! [ -f /usr/share/libtool/config/ltmain.sh ] || \
	cp -f /usr/share/libtool/config/ltmain.sh admin/ltmain.sh
	cp -f /usr/share/aclocal/libtool.m4 admin/libtool.m4.in
	
	make -f admin/Makefile.common cvs

Obviously this may be distro-specific, therefore kdevelop should detect the active distribution and run an appropriate distro-specific shell script to accomplish this task.

I am marking this bug BLOCKER as it should be fixed for R14.
Comment 4 Nikolaus Klepp 2012-11-14 15:31:02 CST
Ok, I copied the files, but "make" failes:

# make -f admin/Makefile.common cvs
*** automake (GNU automake) 1.11.6 found.
*** Creating acinclude.m4
grep: Makefile.am: No such file or directory
*** Creating aclocal.m4
aclocal: `configure.ac' or `configure.in' is required
make: *** [cvs] Fehler 1

root@dasding:/opt/trinity/share/apps/kapptemplate# ls admin/
acinclude.m4.in  config.guess          configure.in.min  detect-autoconf.pl  libtool.m4.in    missing           ylwrap
am_edit          config.pl             cvs.sh            Doxyfile.am         ltmain.sh        mkinstalldirs
bcheck.pl        config.rpath          debianrules       Doxyfile.global     Makefile.am      nmcheck
compile          config.sub            depcomp           doxygen.sh          Makefile.common  oldinclude.m4.in
conf.change.pl   configure.in.bot.end  deps.am           install-sh          Makefile.in      pkg.m4.in

But now things have changed a little bit:

"C++/Simple KDE Application" and "C++/KDE/KFile-module" give the same "libtool: Version mismatch error" as before.

"C/Simple application" and "C++/Simple application" work now.
Comment 5 Timothy Pearson 2012-11-15 21:46:24 CST
I just pushed a relatively large patch into GIT that should resolve these issues.  I have not tested all sample applications, but the ones I have tested now build without incident.
Comment 6 Nikolaus Klepp 2012-11-19 04:11:46 CST
Looks like the patch solved the issue. :-)