KDevelop and autoconf/automake problems.

Fingolfin · n00b Joined: 23 Apr 2002 Posts: 32

These are the versions that I have installed:
kdevelop 2.1-r2
autoconf 2.52d-r1
automake 1.5d-r2

Here is the problem I am having. I emerged Kdevelop with no problems and it loads just fine. I start creating a new project, select Terminal C++, and leave all the default options as they are. I click "create" and get the the two paned window with all the text that flys by as it does its thing. In the top pane, I get this:

*** YOU'RE USING AUTOCONF 2.13. We suggest updating.
*** autoconf 2.5x works best for now, we will drop
*** support for autoconf 2.13 soon.

Its just a warning, nothing serious, but in the bottom pane I get this:

Fingolfin · n00b Joined: 23 Apr 2002 Posts: 32

I finally upgraded to the new autoconf-2.53a and automake-1.6.1-r4. I still get errors when creating a new project in KDevelop, but at leat they're different errors:

Fingolfin · n00b Joined: 23 Apr 2002 Posts: 32

Problem solved by upgrading KDevelop to 2.1.1.

TomorrowPlusX

Hi
I'm not exactly certain *when* the trouble showed up, which is to say, I'm not certain what got emerged and borked this all, but as of tonight, kdevelop will no longer run autoconf/automake. I get this error:

This Makefile is only for the CVS repository
This will be deleted before making the distribution
*** Creating acinclude.m4
!!! If you get recursion errors from autoconf, it is advisable to set the
environment variable M4 to something including "--nesting-limit=500"
*** Creating list of subdirectories
*** Creating configure.in
*** Creating aclocal.m4
*** Creating configure
configure.in:80: error: m4_popdef: undefined macro: AC_Dest
../autoconf/status.m4:831: AC_CONFIG_FILES is expanded from...
configure.in:80: the top level
make[1]: *** [cvs] Error 1
make: *** [all] Error 2
*** failed ***

And if I just type 'make' in my project dir:
cd . && automake --foreign ./Makefile
cd . && perl admin/am_edit Makefile.in
cd . && autoconf
FATAL ERROR: Autoconf version 2.50 or higher is required for this script
make: *** [configure] Error 2

I just went and made sure my autoconf actually is 2.5 or greater (it's 2.53a) and I noticed that the file /usr/bin/autconf is actually a symlink to a perl script in /usr/lib/autoconf which attempts to determine on the fly wether the build environment prefers 2.13 or 2.5 -- so I figure things are as they should be.

So, the question then is, what's going wrong?

TomorrowPlusX · Posted: Thu May 30, 2002 5:23 am Post subject: Let me be more clear

What I meant to say, was, for some reason I'm seeing this problem, even though I'm using KDevelop 2.1.1.

Sad, really.

The good news is that I can still get work done. My old configure script is happy, so I can still modify my various makefile.am's and then run ./configure to put it all together. I jsut have to build everything now *outside* of kdevelop form konsole and use KDevelop as a project management system. *sigh*

TomorrowPlusX · Posted: Thu May 30, 2002 9:26 pm Post subject: Well I'll be damned

Turns out everything is hunky-dory. The trouble is that my current kdevelop project was set up, earlier, with an older version of autoconf. It wasn't an issue until I made some changes to the project which necessitatd a regeneration of the configure script.

I see now, however, that KDevelop can happily create a new project and whatnot, so I'm guessing the trouble came from old, cached scripts/settings from the earlier automake/autoconf.

I just hope I *dont* have to make a new project in KDevelop and then manually migrate all my old files.