>>>>> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes:
Paul> First, IMO warnings aren't good enough.
I agree with you, sincerely I do. Nevertheless Autoconf cannot be
changed like this, we need a general agreement first. Maybe I should
have presented my proposal the other way round: have it use
AC_MSG_ERROR, and then see the reaction. I chose to have it
AC_MSG_WARN, and say I'm in favor of AC_MSG_ERROR.
My fear is that we make it impossible to have a gigantic build tree
mix Autoconf 2.13 and 2.50. It should be possible to mix them.
On a second thought, it wouldn't be impossible.
Let's suppose 2.50 does AC_MSG_ERROR when it meets a
maybe-cross-compiler. It is expected from the people who want to
cross-compile to specify --host, and 2.50 will do the right thing,
included looking for sun4-cc etc.
But 2.13 will not.
So, if the top configure is 2.50, the cross-compiling-person can run
./configure --host=sun4 CC=sun4-cc CXX=sun4-cc
and that should be enough for both configure 2.50 and 2.13 in the
tree.
So again, I think we should have AC_MSG_ERROR everywhere there is
AC_MSG_WARN in the patch. But there lays the lengthy debate :)
Akim
