From: DJ Delorie <dj@redhat.com>
To: neroden@twcny.rr.com
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: [patch] toplevel Makefile.tpl cleanup 6/n
Date: Fri, 14 Mar 2003 20:29:00 -0000 [thread overview]
Message-ID: <200303142029.h2EKTLW10515@greed.delorie.com> (raw)
In-Reply-To: <20030307022619.GA28395@doctormoo> (message from Nathanael Nerode on Thu, 6 Mar 2003 21:26:19 -0500)
> 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.
This one turns out to be wrong. .NOEXPORT: is a target. You made it
the first target. Now if you type "make" (except for GNU make) it
rebuilds the file ".NOEXPORT" and quits.
Please move the pseudo-targets down past the first real target. Given
that top-of-file is bad, bottom-of-file is probably the next best
place (i.e. where they started out from).
prev parent reply other threads:[~2003-03-14 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 2:26 Nathanael Nerode
2003-03-12 19:16 ` Alexandre Oliva
2003-03-14 20:29 ` DJ Delorie [this message]
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=200303142029.h2EKTLW10515@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.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