This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: canadian vs build==host configury (and $with_cross_host)
- From: Tom Tromey <tromey at redhat dot com>
- To: Adam Megacz <megacz at cs dot berkeley dot edu>
- Cc: java-patches at gcc dot gnu dot org
- Date: 19 Jan 2007 15:46:59 -0700
- Subject: Re: canadian vs build==host configury (and $with_cross_host)
- References: <17802.51550.370889.900011@zebedee.pink> <LIYSDAGDHENI64OJKGJELG63FDJ4XGA.458ad753@parallels> <x3hcvpkqrz.fsf_-_@nowhere.com> <x3ac1h0z53.fsf_-_@nowhere.com>
- Reply-to: tromey at redhat dot com
>>>>> "Adam" == Adam Megacz <megacz@cs.berkeley.edu> writes:
# Passing a --with-cross-host argument lets the target libraries know
# whether they are being built with a cross-compiler or being built
# native. However, it would be better to use other mechanisms to make the
# sorts of decisions they want to make on this basis. Please consider
# this option to be deprecated. FIXME.
I wonder what those other mechanisms could be.
Perhaps, if we always use the canonical names for decision-making in
configure.ac, we can just:
if test -z "$with_cross_host"; then
with_cross_host=$build
fi
$with_cross_host should only be empty if the user initially did not
pass --host to configure. So, it should default to the build machine.
Tom