From: Daniel Jacobowitz <drow@false.org>
To: binutils@sources.redhat.com, bje@au.ibm.com
Subject: Re: Use $(SHELL) when running move-if-change
Date: Tue, 21 Dec 2004 03:20:00 -0000 [thread overview]
Message-ID: <20041221032039.GA13097@nevyn.them.org> (raw)
In-Reply-To: <m3zn088jpi.fsf@gossamer.airs.com>
On Mon, Dec 20, 2004 at 09:32:25PM -0500, Ian Lance Taylor wrote:
> Ben Elliston <bje@au.ibm.com> writes:
>
> > Ian Lance Taylor <ian@airs.com> writes:
> >
> > > I'm checking in this patch to bfd/doc/Makefile.am to use $(SHELL)
> > > when running move-if-change. $(SHELL) should always be used with
> > > move-if-change or indeed any shell script. I suppose this one went
> > > unfixed for so long because it is only run when recreating info
> > > files, which normally does not need to be done when using a released
> > > version.
> >
> > While we're discussing move-if-change here is a trivial patch that has
> > been sitting in my tree for some time. I always build with make -s,
> > so this bugs me perhaps more than most. Like mv(1), move-if-change
> > should be silent, too. Okay for mainline?
> >
> > 2004-11-01 Ben Elliston <bje@au.ibm.com>
> >
> > * move-if-change: Don't produce any output, just like mv(1).
>
> Personally I would just as soon keep the top level files in synch with
> gcc as much as possible. So, how about if it is accepted for gcc,
> it's OK for binutils?
>
> If we want to get fancy, we could try this patch:
Please. I find the output valuable when I'm trying to see what was
rebuilt (and the silencing valuable for make -s, too).
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-12-21 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 21:22 Ian Lance Taylor
2004-12-20 23:49 ` Ben Elliston
2004-12-21 2:32 ` Ian Lance Taylor
2004-12-21 3:20 ` Daniel Jacobowitz [this message]
2004-12-21 5:16 ` Ben Elliston
2004-12-21 8:20 ` Nick Clifton
2004-12-21 21:05 ` 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=20041221032039.GA13097@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=bje@au.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).