weird AC_REQUIRE expansion issue

I'm currently trying to understand a weird expansion order issue with Autoconf 2.59 and Automake 1.9.6, and I'd like a hint as to where to search for the bug. A project uses subdir-objects, calls AC_PROG_CC before calling AM_PROG_CC_C_O, yet the code of AC_PROG_CC_C_O (which is AC_REQUIREd by the

Re: weird AC_REQUIRE expansion issue

Hello, On Mon, Aug 29, 2005 at 12:20:02PM +0200, Ralf Wildenhues wrote: A project uses subdir-objects, calls AC_PROG_CC before calling AM_PROG_CC_C_O, yet the code of AC_PROG_CC_C_O (which is AC_REQUIREd by the Automake macro) gets expanded before the AC_PROG_CC macro. Thus, $CC is empty and

Re: weird AC_REQUIRE expansion issue

Hi Stepan, Thanks for your quick reply! * Stepan Kasal wrote on Mon, Aug 29, 2005 at 01:22:18PM CEST: On Mon, Aug 29, 2005 at 12:20:02PM +0200, Ralf Wildenhues wrote: A project uses subdir-objects, calls AC_PROG_CC before calling AM_PROG_CC_C_O, yet the code of AC_PROG_CC_C_O (which is

Re: weird AC_REQUIRE expansion issue

Hello Ralf, AC_DEFUN([CX_COMPILER_CHECKS], [CX_STATUS([compiler checks]) AC_PROG_CC AM_PROG_CC_C_O ... ]) Well, my previous answer was not accurate. The above code should expand AC_PROG_CC between CX_STATUS and AM_PROG_CC_C_O, so it should work. But as soon as CX_COMPILER_CHECKS is

Re: [GNU Autoconf 2.59] testsuite: 67 70 71 73 failed

Hello, On Sun, Aug 28, 2005 at 12:30:27AM +0530, Bharat.V.Adkar wrote: While testing the results of 'make' by 'make check', i got some failure messages. all four failures had the same cause: your system contains a Fortran compiler, ifc, but the binaries created by it cannot be run, because