[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AC_PROG_CC not working
From: |
Morten Eriksen |
Subject: |
AC_PROG_CC not working |
Date: |
06 Oct 2000 15:47:55 +0200 |
User-agent: |
Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.3 |
Hi,
I don't see the expected behavior from the AC_PROG_CC macro. This
configure.in file:
-->8---->8---->8---->8---->8---->8---->8---->8---->8--
AC_INIT(configure.in)
AC_PROG_CC(foo bar supercompiler)
AC_OUTPUT()
-->8---->8---->8---->8---->8---->8---->8---->8---->8--
..will generate this output:
-->8---->8---->8---->8---->8---->8---->8---->8---->8--
checking for gcc... gcc
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for object suffix... o
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for EMX OS/2 environment... no
checking for executable suffix...
checking for foo... (cached) gcc
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
creating ./config.status
-->8---->8---->8---->8---->8---->8---->8---->8---->8--
(This is with the latest Autoconf sources from the head CVS branch.)
The obvious reason for this behavior is that AC_PROG_CC requires
AC_PROG_CPP to run before the AC_PROG_CC macro body. This will then
pick up the gcc compiler (if present) and then use the cached value
for CC, no matter which compilers we specify for AC_PROG_CC.
Any suggestions on how to solve this?
Regards,
Morten
- AC_PROG_CC not working,
Morten Eriksen <=
- Re: AC_PROG_CC not working, Akim Demaille, 2000/10/09
- Re: AC_PROG_CC not working, Pavel Roskin, 2000/10/10
- Re: AC_PROG_CC not working, Akim Demaille, 2000/10/10
- Re: AC_PROG_CC not working, Peter Eisentraut, 2000/10/10
- Re: AC_PROG_CC not working, Pavel Roskin, 2000/10/11