This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[v3, 3.3] Fix configure.in for memory limits
- From: Paolo Carlini <pcarlini at unitus dot it>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Mark Mitchell <mark at codesourcery dot com>
- Date: Thu, 17 Jul 2003 20:09:50 +0200
- Subject: [v3, 3.3] Fix configure.in for memory limits
Hi all, hi Mark,
this fix (reviewed by Phil) is needed for the branch,
otherwise in the common non cross compilation case memory
limits are not imposed when running v3 testsuite, thus using
enormous amounts of memory for some tests.
Ok Mark?
Paolo.
/////////
2003-07-17 Greg Schafer <gschafer@zip.com.au>
* configure.in: Use 'true' and 'false' for
GLIBCPP_IS_CROSS_COMPILING, otherwise memory limits are
not checked when not cross compiling.
* configure: Regenerate.
diff -urN libstdc++-v3-orig/configure.in libstdc++-v3/configure.in
--- libstdc++-v3-orig/configure.in 2003-06-19 21:27:30.000000000 +0200
+++ libstdc++-v3/configure.in 2003-07-17 19:40:54.000000000 +0200
@@ -87,7 +87,7 @@
if test -n "$with_cross_host" || test x"$build" != x"$host"; then
# We are being configured with some form of cross compiler.
- GLIBCPP_IS_CROSS_COMPILING=1
+ GLIBCPP_IS_CROSS_COMPILING=true
# This lets us hard-code the functionality we know we'll have in the cross
# target environment. "Let" is a sugar-coated word placed on an especially
@@ -397,7 +397,7 @@
# We are being configured natively. We can do more elaborate tests
# that include AC_TRY_COMPILE now, as the linker is assumed to be
# working.
- GLIBCPP_IS_CROSS_COMPILING=0
+ GLIBCPP_IS_CROSS_COMPILING=false
CANADIAN=no
# Check for available headers.