Re: Is this a bug in autoconf? (patch included)

[Akim Demaille]

There is something I don't understand very well.  What is it that
config.guess is actually guessing?  Given that it is heavily uname
based, it seems to be pretty much a build-config.guess.

But given that it does use CC, which might be cross, it seems to also
have a host-config.guess flavor, right?

Hm, in fact I think I'm starting to understand the first lines of
config.guess:

# Use $HOST_CC if defined. $CC may point to a cross-compiler
if test x"$CC_FOR_BUILD" = x; then
  if test x"$HOST_CC" != x; then
    CC_FOR_BUILD="$HOST_CC"
  else
    if test x"$CC" != x; then
      CC_FOR_BUILD="$CC"
    else
      CC_FOR_BUILD=cc
    fi
  fi
fi

and afterwards it uses CC_FOR_BUILD.  So it is definitely a
build-config.guess.

Nevertheless, what I don't really understand is the default to
"$HOST_CC".  Why should BUILD_CC default to HOST_CC?  How could using
a HOST_CC, which I understand as a compiler for the HOST we target,
helps understanding the nature of the build system.

Also, what is the intention behind the two different forms of names
(CC_FOR_ vs _CC)?

Hm, lemme think.  Is it that I'm abused by `HOST' in `HOST_CC' which I
should understand as `NATIVE_CC'?

        Akim