This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
with_cross_host vs cross-hosted
- To: gcc-bugs at gcc dot gnu dot org
- Subject: with_cross_host vs cross-hosted
- From: DJ Delorie <dj at redhat dot com>
- Date: Thu, 5 Jul 2001 14:55:48 -0400
My linux-cygwin-cygwin builds have been failing, and I finally took
the time to track it down. In libstdc++-v3, configure uses
${with_cross_host} to choose whether we run a program to generate
std_limits.h, or use default values. Nobody ever sets
${with_cross_host}. I modified configure to explicitly test the
build, host, and target values. Has anyone had any success
cross-building a native?
2001-07-05 DJ Delorie <dj@redhat.com>
* configure.in: Test for cross builds correctly.
* configure: Regenerate.
*** configure.in Fri Jun 15 04:02:09 2001
--- configure.in Thu Jul 5 14:50:36 2001
***************
*** 73,81 ****
GLIBCPP_ENABLE_SJLJ_EXCEPTIONS
! if test -n "$with_cross_host"; then
! # We are being configured with a cross compiler. AC_REPLACE_FUNCS
! # may not work correctly, because the compiler may not be able to
! # link executables.
xcompiling=1
NATIVE=no
--- 73,83 ----
GLIBCPP_ENABLE_SJLJ_EXCEPTIONS
! if test "$build $build" != "$host $target"; then
! # We are being configured with some form of cross compiler.
! # mknumeric_limits may not work correctly, either because the
! # compiler may not run on this machine, may not be able to link
! # executables, or may produce executables we can't run on this
! # machine.
xcompiling=1
NATIVE=no
***************
*** 83,87 ****
# If Canadian cross, then don't pick up tools from the build
# directory.
! if test x"$build" != x"$with_cross_host" && x"$build" != x"$target"; then
CANADIAN=yes
NULL_TARGET=yes
--- 85,89 ----
# If Canadian cross, then don't pick up tools from the build
# directory.
! if test x"$build" != x"$host" && x"$build" != x"$target"; then
CANADIAN=yes
NULL_TARGET=yes