From: Geoff Levand <geoff@infradead.org>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH 2/2] util_lib: Silence ar informational message
Date: Mon, 19 Oct 2015 12:30:36 -0700 [thread overview]
Message-ID: <1445283036.30908.27.camel@infradead.org> (raw)
In-Reply-To: <20151016013855.GC20667@verge.net.au>
Hi Simon,
On Fri, 2015-10-16 at 10:38 +0900, Simon Horman wrote:
> On Thu, Oct 08, 2015 at 04:21:24PM -0700, Geoff Levand wrote:
> > Add the -c option to ar to silence the informational
> > message 'ar creating libutil.a'. ar outputs this
> > message to stderr, and some tools interpret this as
> > a build warning.
>
> I am wondering about the portability of -c.
> I tried to find some documentation of it and drew a blank.
> Do you have any thoughts on this?
I couldn't find any info either. At this point I would say
don't include this.
I'll think about something else. Maybe capture the output
from ar, then only print it if ar returns an error.
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-10-19 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 23:21 [PATCH 2/2] util_lib: Silence ar informational message Geoff Levand
2015-10-16 1:38 ` Simon Horman
2015-10-19 19:30 ` Geoff Levand [this message]
2015-10-20 1:23 ` Simon Horman
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=1445283036.30908.27.camel@infradead.org \
--to=geoff@infradead.org \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
/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