From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ar exit code?
Date: Tue, 9 Mar 2004 12:43:06 +0000 [thread overview]
Message-ID: <d7975749d2e7878d2ac73fbc30065684@vitanuova.com> (raw)
In-Reply-To: <05b901c405d2$88b4ae30$67844051@SOMA>
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
no, ar itself doesn't exit with error status if dupfound
stops it from updating the archive. easy to fix, and it
seems the right thing to me to change it.
[-- Attachment #2: Type: message/rfc822, Size: 2246 bytes --]
From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] ar exit code?
Date: Tue, 9 Mar 2004 13:32:04 +0100
Message-ID: <05b901c405d2$88b4ae30$67844051@SOMA>
> If ar is to create a new archive, but failed because of duplicate symbols,
> it exists with success; mk continues and it is hard to notice untill too
> late.
>
> Is it as it was intended?
mk differs from make in that the whole block of commands
is sent to rc, rather than forking a shell for each command.
that might be the problem.
next prev parent reply other threads:[~2004-03-09 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 10:12 David Tolpin
2004-03-09 12:32 ` boyd, rounin
2004-03-09 12:43 ` C H Forsyth [this message]
2004-03-09 13:07 ` boyd, rounin
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=d7975749d2e7878d2ac73fbc30065684@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).