Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
KDevelop and autoconf/automake problems.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
Fingolfin
n00b
n00b


Joined: 23 Apr 2002
Posts: 32

PostPosted: Mon May 13, 2002 12:25 am    Post subject: KDevelop and autoconf/automake problems. Reply with quote

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:


Code:

shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
[b]aclocal.m4:2824: your implementation of AM_INIT_AUTOMAKE comes from an
aclocal.m4:2824: old Automake version.[\b]  You should recreate aclocal.m4
aclocal.m4:2824: with aclocal and run automake again.
aclocal.m4:1648: invalid unused variable name: `KDE_LDFLAGS'
aclocal.m4:559: invalid unused variable name: `DCOP_DEPENDENCIES'
aclocal.m4:992: invalid unused variable name: `X_LDFLAGS'
aclocal.m4:1710: invalid unused variable name: `USER_LDFLAGS'
aclocal.m4:3702: invalid unused variable name: `IDL_DEPENDENCIES'
aclocal.m4:1234: invalid unused variable name: `KDE_MT_LDFLAGS'
aclocal.m4:3635: invalid unused variable name: `MICO_LDFLAGS'
aclocal.m4:1469: invalid unused variable name: `QT_LDFLAGS'
aclocal.m4:1648: invalid unused variable name: `KDE_LDFLAGS'
aclocal.m4:559: invalid unused variable name: `DCOP_DEPENDENCIES'
aclocal.m4:992: invalid unused variable name: `X_LDFLAGS'
aclocal.m4:1710: invalid unused variable name: `USER_LDFLAGS'
aclocal.m4:3702: invalid unused variable name: `IDL_DEPENDENCIES'
aclocal.m4:1234: invalid unused variable name: `KDE_MT_LDFLAGS'
aclocal.m4:3635: invalid unused variable name: `MICO_LDFLAGS'
aclocal.m4:1469: invalid unused variable name: `QT_LDFLAGS'
aclocal.m4:1648: invalid unused variable name: `KDE_LDFLAGS'
aclocal.m4:559: invalid unused variable name: `DCOP_DEPENDENCIES'
aclocal.m4:992: invalid unused variable name: `X_LDFLAGS'
aclocal.m4:1710: invalid unused variable name: `USER_LDFLAGS'
aclocal.m4:3702: invalid unused variable name: `IDL_DEPENDENCIES'
aclocal.m4:1234: invalid unused variable name: `KDE_MT_LDFLAGS'
aclocal.m4:3635: invalid unused variable name: `MICO_LDFLAGS'
aclocal.m4:1469: invalid unused variable name: `QT_LDFLAGS'
aclocal.m4:1648: invalid unused variable name: `KDE_LDFLAGS'
aclocal.m4:559: invalid unused variable name: `DCOP_DEPENDENCIES'
aclocal.m4:992: invalid unused variable name: `X_LDFLAGS'
aclocal.m4:1710: invalid unused variable name: `USER_LDFLAGS'
aclocal.m4:3702: invalid unused variable name: `IDL_DEPENDENCIES'
aclocal.m4:1234: invalid unused variable name: `KDE_MT_LDFLAGS'
aclocal.m4:3635: invalid unused variable name: `MICO_LDFLAGS'
aclocal.m4:1469: invalid unused variable name: `QT_LDFLAGS'
make[1]: *** [cvs] Error 1
make: *** [all] Error 2


I suspect that the 3rd line about AM_INIT_AUTOMAKE is the root of the problem, and I hear that the autoconf/automake packages aren't backward compatible so maybe I have the wrong versions. Another issure is that the ac-wrapper script that detects weather to use version 2.5 or 2.13 is deciding to use 2.13 instead of 2.5. I tried making all of the auto* symlinks in /usr/bin point to the newer version direclty instead of to ac-wrapper, and that fixed the waring about using autoconf 2.13, but I still got the AM_INIT_AUTOMAKE error. I have no idea what all the invalid unused variable names are about. I cannot compile any projects. I've looked at the forums on www.kdevelop.org, but I didn't find any problems like my own. Can anyone help me out here?
Back to top
View user's profile Send private message
Fingolfin
n00b
n00b


Joined: 23 Apr 2002
Posts: 32

PostPosted: Wed May 29, 2002 1:58 am    Post subject: Upgraded to new autoconf/automake. Still get errors. Reply with quote

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:

Code:

*** 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:103: error: m4_popdef: undefined macro: AC_Dest
../autoconf/status.m4:831: AC_CONFIG_FILES is expanded from...
configure.in:103: the top level
make[1]: *** [cvs] Error 1
make: *** [all] Error 2
*** failed ***



No replys yet, am I the only one with this problem?
Back to top
View user's profile Send private message
Fingolfin
n00b
n00b


Joined: 23 Apr 2002
Posts: 32

PostPosted: Wed May 29, 2002 2:45 am    Post subject: Fixed it. Reply with quote

Problem solved by upgrading KDevelop to 2.1.1.
Back to top
View user's profile Send private message
TomorrowPlusX
Apprentice
Apprentice


Joined: 07 May 2002
Posts: 168
Location: Washington DC, USA

PostPosted: Thu May 30, 2002 5:14 am    Post subject: I've upgraded to KDevelop 2.1.1 and now I have this problem Reply with quote

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?
Back to top
View user's profile Send private message
TomorrowPlusX
Apprentice
Apprentice


Joined: 07 May 2002
Posts: 168
Location: Washington DC, USA

PostPosted: Thu May 30, 2002 5:23 am    Post subject: Let me be more clear Reply with quote

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*
Back to top
View user's profile Send private message
TomorrowPlusX
Apprentice
Apprentice


Joined: 07 May 2002
Posts: 168
Location: Washington DC, USA

PostPosted: Thu May 30, 2002 9:26 pm    Post subject: Well I'll be damned Reply with quote

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.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum