tags 682780 + moreinfo
thanks
On 2012-07-25 17:56 +0200, Sven Joachim wrote:
> The following paragraph from
> /usr/share/doc/autotools-dev/README.Debian.gz is not correct:
>
> ,----
> | BTW, autoconf 2.52+ should enter cross-compiling mode if --host is
> | specified. It will build in cross-compiling mode even if build and host
> | type are the same (this information comes directly from autoconf upstream).
> | This goes against what is in the docs of autoconf 2.59, and it may be a bug
> | somewhere.
> `----
It's still unclear what the _intended_ behavior is, it seems.
> In fact, if both --build and --host are specified and are identical,
> autoconf does not enter cross-compiling mode, as can be seen in
> /usr/share/autoconf/autoconf/general.m4 (the code has been there since
> autoconf 2.50):
>
> ,----
> | if test "x$host_alias" != x; then
> | if test "x$build_alias" = x; then
> | cross_compiling=maybe
> | elif test "x$build_alias" != "x$host_alias"; then
> | cross_compiling=yes
> | fi
> | fi
> `----
However, this code is "to be removed some day". After all, it's only
been there for twelve years.
> The autoconf manual used to be a bit unclear about this in versions
> before 2.69; commit 303e507c2783bb6c43c7c5be2467eaa8a57dadd9 clarified
> the situation.
What I meant was the following paragraph:
,----
| 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' enters cross compilation mode, so it
| doesn't run any tests that require execution.
`----
which seems to imply that `configure' does not enter cross compilation
mode if you specify identical values. However, the same info page also
says:
,----
| Now, `configure' enters cross-compilation mode if and only if
| `--host' is passed.
`----
in contradiction to that assumption (and to the actual, 2.13-compatible,
behavior if --build is not passed).
> This also means that it's actually safe to unconditionally pass
> "--build $(DEB_BUILD_GNU_TYPE) --host $(DEB_HOST_GNU_TYPE)" to
> configure, no matter whether you're cross-building or not (specifying
> only --host and no --build is an error, though).
I'll ask upstream if this is really the case or autoconf 3.0 might
change it.
Cheers,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
