[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Re: updating configure.in to work with Ac 2.5x

From: Stephan Beal
Subject: Fwd: Re: updating configure.in to work with Ac 2.5x
Date: Mon, 27 Aug 2001 12:57:22 +0200

Hello, all,

Per Akim Demaille's request, I'm sending the failing configure.in in. To 
avoid that I miss sending something, I'll simply direct you to the download 


the offending archive is qub-0.6.3.tar.bz2 (there may be a 0.6.4 there by the 
time you see this, in which case please grab that one).

I'm not so much looking for a solution at this point because a) I know you 
guys have plenty to do and b) 2.1x appears to be the most prevelant 
version at the moment (I won't sweat about 2.5 until distros start shipping 
it). I could use some docs/pointers on how to make configure.in compatible 
across AC versions, however. I'll take a look at the docs in CVS, per Akim's 
suggestion from an earlier mail.

The failure message you should get with the above archive (and AC 2.52) is:
configure.in:245: error: m4_popdef: undefined macro: 
acgeneral.m4:3399: AC_CONFIG_FILES is expanded from... 
configure.in:245: the top level 

configure.in:245 is the end of the script, however, and there is nothing 
It works find with AC 2.13, however.

Take care,

----- stephan

----------  Forwarded Message  ----------

Subject: Re: updating configure.in to work with Ac 2.5x
Date: 27 Aug 2001 12:54:40 +0200
From: Akim Demaille <address@hidden>
To: Stephan Beal <address@hidden>
Cc: address@hidden

>>>>> "Stephan" == Stephan Beal <address@hidden> writes:

Stephan> Are there documents explaining what needs to be done to make
Stephan> older configure.ins work with AC 2.5x? I've checked out the
Stephan> manual on the GNU site and it's dated 1998 and covers 2.13,
Stephan> so little luck there. I would be especially interested in
Stephan> docs which explain how I can make my configure.in portable
Stephan> across 2.5x and 2.1x. Or are the two incompatible?

Somewhat.  The CVS version of Autoconf has documentation about that.
Your problem is a new one.  Please, send all the relevant data (such
as configure.in) to bug-autoconf.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]