Version: 3.0.0b1 (using KDE 3.1.93 (CVS >= 20031028), compiled sources) Compiler: gcc version 2.95.3 20010315 (SuSE) OS: Linux (i686) release 2.4.18-4GB using autoconf-2.57, automake-1.7.8 Create simple C++ hello project with appwizard Run auto....friends: make -f Makefile.cvs aclocal aclocal: configure.in: 8: macro `AM_PROG_LIBTOOL' not found in library make: *** [all] Error 1 dnl-ing the line 8 of the configure.in solves the problem - project builds, but without libtool, of course.
I *think* that this will fix itself if you use autoconf 2.57a
Where to get it ? Have taken a look on the ftp.gnu.org and there is nothing like autoconf-2.57a. There is 2.58 which requests automake-1.7a which again is not present on gnu site. What is going on ?
ftp://alpha.gnu.org/gnu/autoconf/ It's listed there, but not from the main autoconf page I wonder if 2.58 is meant as a replacement for something wrong with 2.57a?
OK. Then it is alpha. I even did not know for alpha.gnu.org ... However, I think it is the admin directory and I think the one of aclocal.whatever files which does not contain the macro in question anymore. Is it moved to the autoconf or what ? The whole thing stopped to work "properly" not longer than 2 months ago. And, is it safe to use the alpha version of something as important as the autoconf and automake are ?
Is this still valid ??
Of course ! autoconf-2.57, automake-1.7.8, KDevelop-CVS20031129 (later on it does not build) gmake -f Makefile.cvs aclocal aclocal: configure.in: 8: macro `AM_PROG_LIBTOOL' not found in library gmake: *** [all] Error 1 I can not accept the upgrade to unstable or/and unofficial auto* version as proposed by Caleb. And he even left the thread in the middle ... And more, the KDevelop requirements list autoconf >= 2.52 and automake >= 1.6
yes, it should simply work. It does work here. autoconf = 2.57 automake = 1.7.2
So: 1. it should work for automake >= 1.6 (by www.kdevelop.org) 2. it works for 1.7.2 (by ACL) 3. it does not for 1.7.8 (by my poor self) ???? Should the bug stay open or are the first two claims enough to tag the bug resolved ????
Shouldn't libtool be installed ? Afaik this is the one that offers two file called libtool.m4 and ltdl.m4 in /usr/share/aclocal/ and those are needed for for the autotools to include the proper macro. My libtool version is 1.5, so can the guys who have trouble with this try this out ?
O.K. now I understand. If I take a look into the project generated by the KDevelop-2 as well as the KDevelop-3 CVS itself, they contain the admin directory with the proper libtool.m4.in template which (am I right ?) overrides the usage of /usr/share/aclocal/libtool.m4. That is why KDevelop-2 projects and KDevelop-3 CVS building work for me with newer autoconf and automake. The simple C++ hello project generated with Kdevelop-3 lacks proper libtool macro templates which are then used as provided by the system so it doesn't build with my versions of autotools which are newer as installed from the SuSE-8.1 distro. So, is this the feature or bug ? If feature, please update the requirements page of the KDevelop-3. With the explanation of possible troubles with having two libtool installations in the system. BTW, my libtool is 1.4.1. SuSE-8.1 distro dates Oct 2002 and it seems as being obsolete. So much about stable production enviroment ...
I too have two diferent versions. ~> libtool --version ltmain.sh (GNU libtool) 1.4.2 (1.922.2.53 2001/09/11 03:18:52) ~>cd kdevelop kdevelop> libtool --version ltmain.sh (GNU libtool) 1.5a (1.1240 2003/06/26 06:55:19)
Just the same here. But just invoking the libtool binary does not mean that the right libtool.m4 is used. Yet, we may trust the libtool creators that it handles it right, can't we ? So, obviously I am already using the right libtool and this thread shows up a bug and not the feature. And it seems to be related to autoconf/make and not to libtool. Am I right or not ?
*** Bug 69593 has been marked as a duplicate of this bug. ***
As of 3.0.2, the KDevelop templates should work with the latest autotools. With the right combination of libtool/automake/autoconf this problem doesn't occur, with some combinations it does. Either way, I don't think it can be called a bug in KDevelop anymore.
The bug is that the package dependency list does not include libtool. After you have installed KDevelop on a virgin system, the Hello World template application fails to build. It builds after you install libtool manually. Fix requested: add libtool to the dependency list.
No, adding a dep on libtool to KDevelop is wrong, because KDevelop works perfectly fine without libtool, autoconf or automake. It supports other buildsystems and also languages other than C++. And at least on Debian Kdevelop does recommends libtool so everybody ignoring that deserves a failing hello world project.
When exactly does KDevelop recommend installing libtool? I did not ignore it, I just did not see it (KUbuntu).
In the package information. Have a look at the kdevelop package, libtool should be listed in the Recommends section, at least thats the case on Debian. If thats not the case in the KUbuntu package you should file a bug to KUbuntu.