On Jun 27, 2000, Pavel Roskin <[EMAIL PROTECTED]> wrote:
> But is it safe for old versions of Autoconf?
Nope, it isn't safe. The current CVS version of autoconf is totally
incompatible with the last release. I'm trying to fix that, but I'm,
how should I say, encountering some resistance :-)
Specifying only TRIPLET should continue to work. Specifying
--host=TRIPLET will not have, in CVS autoconf, the same effect of
--host=TRIPLET used to have in the last release of autoconf. I hope
to arrange for it to keep overriding the default of --build, at least
for a couple of years.
> Will it have the same effect if e.g. config.guess fails to recognize
> the architecture?
IMO, specifying the TRIPLET alone is the way to go, at least for now.
> If it is, we should recommend RPM developers to add "--build" before
> %{_target_platform}
Not yet, because there are very little packages that will do The Right
Thing (TM) given that option. Most released packages, and all those
that will still be released with autoconf 2.13, will use --build only
to set the $build_* variables, and guess --host, which is obviously
wrong, but it's the way it has worked for years.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
