----- "Max Matveev" <makc@xxxxxxxxx> wrote:
> It all started when I've tried to compile PCP on Solaris using Sun's
> compiler instead of the default CC: I was greated by messages like
> ...
> After some on and off attempts to get to the bottom of this I've
> finally traced it to this particular bit in configure.in
>
> dnl check if user wants their own C compiler
> if test -z "$CC"; then
> AC_PROG_CC
> fi
> cc=$CC
>
> If CC in set in the environment then the whole set of checks is
> skipped and, as side effect, the value of ac_objext is not set, so
> ...
> IIRC the test was (in various) forms in configure from its inception
> back in '99. I think it's time to kill it - AC_PROG_CC is capable and
> willing to take CC from the enviroment, we're not going to loose any
> functionality if it is removed and will actually gain support for
> non-default compilers.
*nod* ... from the autoconf manual:
Macro: AC_PROG_CC ([compiler-search-list])
Determine a C compiler to use. If CC is not already set in the environment,
check for gcc and cc, then for other C compilers. Set output variable CC to the
name of the compiler found.
So, we should just be able to remove the conditional CC check there,
as you say.
cheers.
--
Nathan
|