[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
--build and --host
From: |
Steve M. Robbins |
Subject: |
--build and --host |
Date: |
Thu, 14 Feb 2002 10:17:16 -0500 |
User-agent: |
Mutt/1.3.27i |
Hello,
In case Henrique's posting wasn't clear, the question is this: is
./configure --build=foo ...
different from
./configure --build=foo --host=foo ...
or not? In other words, does configure change its behaviour (e.g. go
into "cross compiling" mode) as soon as --host is specified, even when
the host type is the same as the build type?
There are conflicting pieces of evidence. The first two suggest
that cross compiling happens only if host != build. The second
two suggest that things change as soon as you specify --host, no
matter what the value you give it.
1. The autoconf doc (node System Type) says
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the host
platform (i.e., that on which the generated programs will eventually be
run) with `--host=TYPE'. In this case, you should also specify the
build platform with `--build=TYPE', because, in this case, it may not
be possible to guess the build platform (it sometimes involves
compiling and running simple test programs, and this can't be done if
the compiler is a cross compiler).
[ well, on second reading, I'm not sure what this says about
host == build ... ]
2. The autoconf doc (node Specifying Names) says
They all default to the result of running `config.guess', unless you
specify either `--build' or `--host'. In this case, the default
becomes the system type you specified. If you specify both, and
they're different, `configure' will enter cross compilation mode, so it
won't run any tests that require execution.
3. Generated configure scripts have this bit
ac_tool_prefix=
test -n "$host_alias" && ac_tool_prefix=$host_alias-
4. Akim posted a note saying
- passing --host means you cross compile (whatever the relationship
between host and build)
[http://sources.redhat.com/ml/autoconf/2002-02/msg00059.html]
So, we really just wanted to know which is the truth?
Thanks,
-Steve
--
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants
- Re: Why was handling of program_prefix changed?, (continued)
- Re: Why was handling of program_prefix changed?, Akim Demaille, 2002/02/07
- Re: Why was handling of program_prefix changed?, Ian Lance Taylor, 2002/02/07
- Re: Why was handling of program_prefix changed?, Akim Demaille, 2002/02/11
- Re: Why was handling of program_prefix changed?, Maciej W. Rozycki, 2002/02/11
- Re: Why was handling of program_prefix changed?, Akim Demaille, 2002/02/11
- Re: Why was handling of program_prefix changed?, Ian Lance Taylor, 2002/02/11
- Re: Why was handling of program_prefix changed?, Tom Tromey, 2002/02/11
- Re: Why was handling of program_prefix changed?, Henrique de Moraes Holschuh, 2002/02/13
- Re: Why was handling of program_prefix changed?, Ralf Corsepius, 2002/02/14
- Re: Why was handling of program_prefix changed?, Henrique de Moraes Holschuh, 2002/02/14
- --build and --host,
Steve M. Robbins <=
- Re: --build and --host, Ralf Corsepius, 2002/02/14
- Re: --build and --host, Steve M. Robbins, 2002/02/14
- Re: --build and --host, Akim Demaille, 2002/02/28
- Re: --build and --host, Henrique de Moraes Holschuh, 2002/02/28
- Re: --build and --host, Steve M. Robbins, 2002/02/28
- Re: --build and --host, Henrique de Moraes Holschuh, 2002/02/28