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

[Pavel Roskin]

Salut, Akim :-)

> This is why I would like to reiterate a proposal I made: get rid of
> AC_CANONICAL_{BUILD, TARGET, HOST}, and provide only
> AC_CANONICAL_SYSTEM.

I still want to have choice between three situations:

1) configure is not aware of BUILD and HOST. config.{guess,sub} are not
ditributed. --build, --host and --target cause warnings.

2) configure is aware of BUILD and HOST. config.{guess,sub} are
ditributed. --build and --host are accepted, --target causes a warning.
This should be enabled by AC_CANONICAL_HOST.

3) configure is aware of BUILD, HOST and TARGET. This should be enabled by
AC_CANONICAL_SYSTEM.

Irrelevant options should not cause errors because the top-level configure
may be target-aware, whereas configure in a subdirectory may be not
target-aware.

I don't want to force people into AC_CANONICAL_SYSTEM just for BUILD
variables.

If AC_CANONICAL_HOST is used and config.{guess,sub} are distributed anyway
it would be nice to have BUILD support. Whenever HOST makes sense, BUILD
makes sense too.

I don't want people using --target when it's irrelevant without being
warned.

Pavel