| Salut, Akim :-)
Moin moin!
(Well, I don't know what this means, but it sounds very friendly :)
There's a guy on some mailing list who starts each of his messages
with `moin moin').
| > 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.
Cause warnings!?! Hm. Sounds a bit hard, but doable. But I'm not
sure to understand what would make it so interesting?
| 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.
Well, I must confess my approach to this situation is much more
related based on the beauty of the code and of the interface we
provide, than with the intention of addressing such problems (since I
never had to face them). If you consider this is a serious issue,
that there are truly people who get trapped with this, then we could
introduce a special case for 2.
| 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.
Well, what you propose computes HOSTS additionally, and using SYSTEM
will be extremely fast, since it is just re-decoding $build. Really,
I don't think the cost issue can really matter here. I wouldn't be
surprised to learn that configure spends more time in option
processing alone.
| 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.
Why? People which reached such a competence level that they
cross-compile would really use --target to something for which it
makes no sense?
Akim
