From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com
Subject: [patch] toplevel Makefile.tpl cleanup 6/n
Date: Fri, 07 Mar 2003 02:26:00 -0000 [thread overview]
Message-ID: <20030307022619.GA28395@doctormoo> (raw)
Obvious rearrangement and commenting; it's best if these are right up
top where they're easily identified.
* Makefile.tpl: Move .NOEXPORT, MAKEOVERRIDES up.
* Makefile.in: Regenerate.
--- Makefile.tpl.old 2003-02-28 13:05:21.000000000 -0500
+++ Makefile.tpl 2003-02-28 16:40:56.000000000 -0500
@@ -23,6 +23,10 @@
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
#
+# Don't pass command-line variables to submakes.
+.NOEXPORT:
+MAKEOVERRIDES=
+
# -------------------------------
# Standard Autoconf-set variables
# -------------------------------
@@ -1425,7 +1429,3 @@
AUTOCONF = autoconf
$(srcdir)/configure: @MAINT@ $(srcdir)/configure.in $(srcdir)/config/acx.m4
cd $(srcdir) && $(AUTOCONF)
-#
-
-.NOEXPORT:
-MAKEOVERRIDES=
next reply other threads:[~2003-03-07 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 2:26 Nathanael Nerode [this message]
2003-03-12 19:16 ` Alexandre Oliva
2003-03-14 20:29 ` 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=20030307022619.GA28395@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.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