From: Nick Clifton <nickc@redhat.com>
To: Shaun Jackman <sjackman@gmail.com>
Cc: binutils@sources.redhat.com
Subject: Re: objcopy fails silently with an empty input file
Date: Fri, 15 Apr 2005 09:13:00 -0000 [thread overview]
Message-ID: <425F8537.1070202@redhat.com> (raw)
In-Reply-To: <7f45d93905041408251402df05@mail.gmail.com>
Hi Shaun,
> Sorry, Nick . I wasn't clear. The use case I posted was the behaviour
> that I desired, which I get with the patch I posted. With your patch,
> I see the same behaviour as you do. To clear things up, I would like
> "empty input file" to be a warning, not an error, particularly when
> the input BFD is 'binary'.
Ah - unfortunately I do not think that this is a good idea. The input
file could be empty for a variety of reasons - it could be a device, a
pipe, or some other kind of system file, instead of just an ordinary,
zero-sized file.
Besides - what is the value in creating an output file from an empty
input file ? What possible use can this output file have ?
Cheers
Nick
next prev parent reply other threads:[~2005-04-15 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 23:35 Shaun Jackman
2005-04-13 16:08 ` Nick Clifton
2005-04-13 17:21 ` Shaun Jackman
2005-04-14 9:54 ` Nick Clifton
2005-04-14 15:25 ` Shaun Jackman
2005-04-15 9:13 ` Nick Clifton [this message]
2005-04-15 16:01 ` Shaun Jackman
2005-04-15 16:27 ` 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=425F8537.1070202@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=sjackman@gmail.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).