>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> And are you sure their authors will be happy to see their script
>> still working, but doing something different?
Alexandre> Why would they be doing something different?
I don't know too well, and I confess and don't want to :) I find the
old rules obscure, and the interaction between HOST on the one hand,
and the three options on the other hand was completely derstable (I
needed a ununderstandable, and didn't choose overstandable :).
Alexandre> You mean, because now they'd be considered to be cross
Alexandre> compiling? Hmm... I think I begin to understand why the
Alexandre> current implementation is as it is.
By current you mean CVS, not the current proposal, right?
Alexandre> If you specify TRIPLET, it will set a default for all of
Alexandre> build, host and target, unless they're explicitly
Alexandre> overridden by --host, --build or --target arguments. So
Alexandre> why not retain this behavior?
Are you sure that's what the rule was? Hm, the text sounds like this,
but the implementation was much more painful than this:
# Do some error checking and defaulting for the host and target type.
# The inputs are:
# configure --host=HOST --target=TARGET --build=BUILD NONOPT
#
# The rules are:
# 1. You are not allowed to specify --host, --target, and nonopt at the
# same time.
# 2. Host defaults to nonopt.
# 3. If nonopt is not specified, then host defaults to the current host,
# as determined by config.guess.
# 4. Target and build default to nonopt.
# 5. If nonopt is not specified, then target and build default to host.
Anyway, Ian did spot (desired) incompatibilities with the new
defaults, but I don't know/recall which ones.
Alexandre> It can be done in a much simpler way: when you encounter
Alexandre> any such argument, just set the host, build and target
Alexandre> variables that are still set to NONE.
It seems to me you are saying we moved from `./configure HOST' to
`./configure BUILD', given the defaults. Aren't you?
Akim
