Still doing tests with KDevelop 2.1.3 and different autoconf / automake combinations and that is what I found.
these ones work for me from KDevelop 2.1.3
autoconf 2.13 / automake 1.4-p6
autoconf 2.52 / automake 1.4-p6
autoconf 2.53 / automake 1.4-p6
autoconf 2.53 / automake 1.6.3
Didn't work for me
autoconf 2.54 / automake 1.7.1
autoconf 2.54 / automake 1.4-p6
autoconf <2.54 / automake 1.7.1 *
* automake 1.7.1 requieres autoconf 2.54 or greater
The most recent version of each one that works with KDevelop is automake 1.6.3 & autoconf 2.53. Autoconf 2.54 fail no matter which automake I use giving the
m4_popdef: undefined macro: AC_Dest
I hope this help
Mario
_________________________________________________________________From: David Walser <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Cooker] Kdevelop problem Date: Tue, 29 Oct 2002 14:14:38 -0800 (PST)--- Quel Qun <[EMAIL PROTECTED]> wrote: > On Tue, 2002-10-29 at 11:10, Mario Vazquez wrote: > > When creating a simple C project from KDevelop > Project --> New... I got > > this error: > > > > > > configure.in:101: error: m4_popdef: undefined > macro: AC_Dest > > autoconf/status.m4:844: AC_CONFIG_FILES is > expanded from... > > configure.in:101: the top level > > autom4te: /usr//bin/m4 failed with exit status: 1 > > make[1]: *** [cvs] Error 1 > > make: *** [all] Error 2 > > sh: line 1: ./configure: No such file or directory > > > > > > Packages installed: > > > > kdevelop-2.1.3-7 > > kdebase-3.1-0.beta2.17 > > kdelibs-3.1-0.beta2.11 > > autoconf-2.13-15 > > autoconf2.5-2.54-1 > > automake1.6-1.7.1-2 > > > > Also tried latest sources of automake 1.7.1 and > autoconf 2.54 directly from > > GNU Org. > > > You should not use autoconf2.5 and automake1.6, you > shouldn't even have > them installed together, so or you are not using > cooker, or you forced > the install. In either case, you are on your own. > Sorry. > > $ urpmf --conflicts kdevelop > kdevelop:conflicts:automake1.6 old news, we have no workaround for this currently > kdevelop:conflicts:autoconf2.5 and this is the one that doesn't make sense. We have the autoconf packages made so that they can coexist peacefully. Is there still an outstanding issue with it? What is it? Let's fix it! Nothing AFAIK requires automake1.6, but all kinds of stuff requires autoconf2.5, we shouldn't have it conflicting with kdevelop. __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
