[Top][All Lists]

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

Re: Why do I need both AC_INIT and AM_INIT_AUTOMAKE???

From: Earnie Boyd
Subject: Re: Why do I need both AC_INIT and AM_INIT_AUTOMAKE???
Date: Tue, 08 Apr 2003 07:04:17 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

Eric Siegerman wrote:

That usage of AM_INIT_AUTOMAKE is deprecated.  You do need to
call it -- but you should be able to do so with no arguments:

This is a requirement of Cygwin's autoconfigury tools if you want to use the most current versions of autoconf, otherwise you get 2.13 versions by default.

    AC_INIT(atlc, 4.2.12, address@hidden)

See the description of AM_INIT_AUTOMAKE in the manual.

(The form you've been using dates from a time when AC_INIT did
*not* accept package-name and version arguments.
AM_INIT_AUTOMAKE still accepts those values for backward
compatibility, but providing them in AC_INIT instead is now

- see below, despite the fact I have run 'aclocal',
which is from automake 1.7 and not an old version of automake I have
lying around as the error message suggests.

Although your "aclocal" program is from 1.7, it's possibly
reading the data files from an older version of Automake.  If you
change your as I've suggested, and get complaints
about missing arguments to AM_INIT_AUTOMAKE (or other weird
errors suggesting that Automake doesn't know the package's name
or version), I'd raise that from "possible" to "almost certain" :-)

I raise that to most certainly now.


reply via email to

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