Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gcc-patches@gcc.gnu.org
Cc: dj@redhat.com, binutils@sources.redhat.com,
	gdb-patches@sources.redhat.com
Subject: [patch] move libstdcxx_flags near where it's used
Date: Wed, 19 Jun 2002 14:09:00 -0000	[thread overview]
Message-ID: <20020619210820.GA25316@doctormoo.dyndns.org> (raw)

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


             reply	other threads:[~2002-06-19 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 14:09 Nathanael Nerode [this message]
2002-06-19 16:53 ` DJ Delorie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020619210820.GA25316@doctormoo.dyndns.org \
    --to=neroden@doctormoo.dyndns.org \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox