[Top][All Lists]

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

Re: Report of a problem with autoconf-2.52 about divert

From: Akim Demaille
Subject: Re: Report of a problem with autoconf-2.52 about divert
Date: 09 Aug 2001 09:57:40 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Academic Rigor)

| I don't know if it is really a bug or if I misuse autoconf in any
| way. Any help will be welcome and thanks for replying (if any) by
| using my email (as I said I'am not subscribed to any list).

Due to insecure code in Automake.  Here is what the Autoconf doc says:

New Macros

   Because Autoconf has been dormant for years, Automake provided
Autoconf-like macros for a while.  Autoconf 2.50 now provides better
versions of these macros, integrated in the `AC_' namespace, instead of
`AM_'.  But in order to ease the upgrading via `autoupdate', bindings
to such `AM_' macros are provided.

   Unfortunately Automake did not quote the name of these macros!
Therefore, when `m4' find in `aclocal.m4' something like
replaced with its Autoconf definition.

   Fortunately Autoconf catches pre-`AC_INIT' expansions, and will
complain, in its own words:

     $ cat configure.in
     $ aclocal-1.4
     $ autoconf
     ./aclocal.m4:17: error: m4_defn: undefined macro: _m4_divert_diversion
     actypes.m4:289: AM_TYPE_PTRDIFF_T is expanded from...
     ./aclocal.m4:17: the top level

   Future versions of Automake will simply no longer define most of
these macros, and will properly quote the names of the remaining macros.
But you don't have to wait for it to happen to do the right thing right
now: do not depend upon macros from Automake as it is simply not its job
to provide macros (but the one it requires by itself):

     $ cat configure.in
     $ rm aclocal.m4
     $ autoupdate
     autoupdate: `configure.in' is updated
     $ cat configure.in
     $ aclocal-1.4
     $ autoconf

reply via email to

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