Re: Bug#369396: Regression: problems with macro calling AC_PROG_CC and AC_C_BIGENDIAN

[Ralf Wildenhues]

Hi Stepan,

* Stepan Kasal wrote on Wed, May 31, 2006 at 11:14:50AM CEST:
> On Tue, May 30, 2006 at 08:19:14AM +0200, Ralf Wildenhues wrote:
> > I guess you could instead also m4_define TEST_INIT, so that it will not
> > take part in the requirement-diversion game.  That should preserve the
> > order as well.
> 
> no, this won't work; AC_REQUIRE has to be called inside an AC_DEFUNed
> macro.  Autoconf will complain:

Right.  You could put the requirement in another defun'ed macro that
you'd call from the m4_define'd TEST_INIT then, though.  Same effect.
;-)

> configure.ac:12: error: AC_REQUIRE(AC_PROG_CC): cannot be used outside of an 
> m4_defun'd macro
> configure.ac:12: the top level
> 
> (AC_DEFUN is the same as m4_defun).

Not to aclocal, it isn't.  Only to the requirement-diversion machinery,
m4_require/AC_REQUIRE and m4_defun/AC_DEFUN are alike, respectively.

Cheers,
Ralf