This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
[patch] move libstdcxx_flags near where it's used
- From: Nathanael Nerode <neroden at doctormoo dot dyndns dot org>
- To: gcc-patches at gcc dot gnu dot org
- Cc: dj at redhat dot com, binutils at sources dot redhat dot com,gdb-patches at sources dot redhat dot com
- Date: Wed, 19 Jun 2002 17:08:20 -0400
- Subject: [patch] move libstdcxx_flags near where it's used
Patch to top level configure to relocate the defintion of
libstdcxx_flags.
It's only used in one place in all of configure and configure.in, and it
was defined WAAAY above that place. This was confusing me for a long
time, since I thought there must be a reason for this. But there
wasn't. (This will break my first reorg patch, but if it's accepted
I'll resumbit it without that part).
Tested on i686-pc-linux-gnu, no changes.
2002-06-19 Nathanael Nerode <neroden@twcny.rr.com>
* configure.in: Move definition of libstdcxx_flags
right above usage, rather than waaay earlier.
Index: configure.in
===================================================================
RCS file: /cvsroot/gcc/gcc/configure.in,v
retrieving revision 1.155
diff -u -r1.155 configure.in
--- configure.in 19 Jun 2002 17:39:21 -0000 1.155
+++ configure.in 19 Jun 2002 21:04:42 -0000
@@ -45,8 +45,6 @@
host_libs="intl mmalloc libiberty opcodes bfd readline db tcl tk tclX itcl tix libgui zlib"
libstdcxx_version="target-libstdc++-v3"
-# Don't use libstdc++-v3's flags to configure/build itself.
-libstdcxx_flags='`case $$dir in libstdc++-v3 | libjava) ;; *) test ! -f $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags || $(SHELL) $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags --build-includes;; esac` -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src/.libs'
# these tools are built for the host environment
# Note, the powerpc-eabi build depends on sim occurring before gdb in order to
@@ -1568,6 +1566,8 @@
*) GCJ_FOR_TARGET=$GCJ_FOR_TARGET' $(FLAGS_FOR_TARGET)' ;;
esac
+# Don't use libstdc++-v3's flags to configure/build itself.
+libstdcxx_flags='`case $$dir in libstdc++-v3 | libjava) ;; *) test ! -f $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags || $(SHELL) $$r/$(TARGET_SUBDIR)/libstdc++-v3/testsuite_flags --build-includes;; esac` -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src -L$$r/$(TARGET_SUBDIR)/libstdc++-v3/src/.libs'
if test "x${CXX_FOR_TARGET+set}" = xset; then
:
elif test -d ${topsrcdir}/gcc; then