Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geoff Levand <geoff@infradead.org>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH 2/2] util_lib: Silence ar informational message
Date: Fri, 16 Oct 2015 10:38:56 +0900	[thread overview]
Message-ID: <20151016013855.GC20667@verge.net.au> (raw)
In-Reply-To: <1444346484.29301.81.camel@infradead.org>

Hi Geoff,

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?

> Signed-off-by: Geoff Levand <geoff@infradead.org>
> ---
>  util_lib/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/util_lib/Makefile b/util_lib/Makefile
> index 54ccdc5..15b84e5 100644
> --- a/util_lib/Makefile
> +++ b/util_lib/Makefile
> @@ -18,5 +18,5 @@ $(UTIL_LIB): CPPFLAGS += -I$(srcdir)/util_lib/include
>  
>  $(UTIL_LIB): $(UTIL_LIB_OBJS)
>  	@$(MKDIR) -p $(@D)
> -	$(AR) rs $(UTIL_LIB) $(UTIL_LIB_OBJS)
> +	$(AR) rs -c $(UTIL_LIB) $(UTIL_LIB_OBJS)
>  
> -- 
> 2.5.0
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-10-16  1:39 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 [this message]
2015-10-19 19:30   ` Geoff Levand
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=20151016013855.GC20667@verge.net.au \
    --to=horms@verge.net.au \
    --cc=geoff@infradead.org \
    --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