On Apr 21, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> There are a couple of problems with this approach. It compares the
> result of running config.guess to what the user passed in with
> --host, but I am not sure we actually want the configure script to
> continue to think it is running on a i686-pc-linux-gnu host when it
> is actually using a cross compiler.
configure is run on the *build* platform, so setting host to NONE as
you do is totally wrong, because it will cause configure to assume
host and build are the same platform. When the user specifies --host,
he's explicitly telling configure they're not. What you want to do is
to compare $host with $build.
> If the autoconf script uses host values to make compile time
> decisions, then they will be wrong because we are using a cross
> compiler.
If it uses *host* values, it will be right, because the *host*
platform is that on which the built program will run. You probably
mean *build* values here, and then you're right, and it is indeed
something the developer should worry about.
> http://peti.cys.de/autoconf-archive/Miscellaneous/acx_check_pathname_style.html
> This test will break if you use a cross compiler with cygwin.
No, it is correct, because it decides what pathname style to use
depending on *host*. If it depended on the *build* platform, it would
indeed be broken.
> So who is at fault here?
You're just misunderstanding the nomenclature.
> Should autoconf know about the host it is running under and the
> cross "host" info?
Yep. That's what AC_CANONICAL_BUILD is for.
--
Alexandre Oliva Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
