On 04/22/2012 11:42 AM, Bruno Haible wrote: > Hi, > > On bi-arch systems (such as x86 / x86_64) it is often necessary to pass > the --host option together with an appropriate value for CC. But this > triggers a warning: > > $ ./configure --host=i686-pc-linux-gnu CC="gcc -m32 -march=i586" > configure: WARNING: if you wanted to set the --build type, don't use --host. > If a cross compiler is detected then cross compile mode will be used > ... > > This warning was introduced on 2000-06-30, in commit > <http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=cb2e761b8e1181f97e8e09d85526bd22078433db> > with the remark "Re-enable the old behavior of --host and --build." > > This warning was meant to warn users about a changed semantics of > --build and --host. This change is now 12 years in the past; users > have had enough time to learn it. I therefore suggest to remove the > warning.
This is the clincher - it's only a warning, and by now, people have migrated to saner usage patterns with the modern semantics of --build and --host. I will go ahead and apply this. > if test "x$build_alias" = x; then > cross_compiling=maybe > - AC_MSG_WARN([if you wanted to set the --build type, don't use --host. > - If a cross compiler is detected then cross compile mode will be used]) > elif test "x$build_alias" != "x$host_alias"; then > cross_compiling=yes > fi > > > -- Eric Blake [email protected] +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
