From: "H. J. Lu" <hjl@lucon.org>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: PR binutils/4348: strip can't strip sections
Date: Thu, 12 Apr 2007 15:00:00 -0000 [thread overview]
Message-ID: <20070412134955.GA12301@lucon.org> (raw)
In-Reply-To: <461E191E.5010102@redhat.com>
On Thu, Apr 12, 2007 at 12:33:50PM +0100, Nick Clifton wrote:
> Hi H. J.
>
> >I don't see why objcopy should stop when there are no sections to be
> >copied. After all, the resulting output file is still valid ELF
> >file.
>
> I agree that the tools should not fail. But they also should tell the
> user that nothing has happened. Otherwise the user will never know that
> their objcopy/strip command was pointless and they may then consider it
> a bug that nothing has changed.
Something is changed in my testcase: 3 sections are removed. Even
if nothing has changed, do we warn the second strip on the same
file:
# strip x.o
# strip x.o
H.J.
next prev parent reply other threads:[~2007-04-12 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 6:36 H. J. Lu
2007-04-12 13:22 ` Nick Clifton
2007-04-12 15:00 ` H. J. Lu [this message]
2007-04-12 20:35 ` Nick Clifton
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=20070412134955.GA12301@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).