From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Silence libtool during link
Date: Mon, 7 Nov 2022 13:16:54 -0500 [thread overview]
Message-ID: <5227d2fb-26fa-907f-de4a-3cdcb47ae813@simark.ca> (raw)
In-Reply-To: <20221107181353.68359-1-tromey@adacore.com>
On 11/7/22 13:13, Tom Tromey via Gdb-patches wrote:
> The switch to linking with libtool now shows a very long link line
> even when V=0. This patch arranges to silence libtool in this
> situation.
> ---
> gdb/Makefile.in | 2 +-
> gdb/silent-rules.mk | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/Makefile.in b/gdb/Makefile.in
> index 522fc20bccd..0f5df2ccb7b 100644
> --- a/gdb/Makefile.in
> +++ b/gdb/Makefile.in
> @@ -148,7 +148,7 @@ LIBTOOL = @LIBTOOL@
> # Set this up with gcc if you have gnu ld and the loader will print out
> # line numbers for undefined references.
> #CC_LD = g++ -static
> -CC_LD = $(LIBTOOL) --mode=link $(CXX) $(CXX_DIALECT)
> +CC_LD = $(LIBTOOL) $(SILENT_FLAG) --mode=link $(CXX) $(CXX_DIALECT)
>
> # Where is our "include" directory? Typically $(srcdir)/../include.
> # This is essentially the header file directory for the library
> diff --git a/gdb/silent-rules.mk b/gdb/silent-rules.mk
> index c2c43481296..36791f6683f 100644
> --- a/gdb/silent-rules.mk
> +++ b/gdb/silent-rules.mk
> @@ -18,4 +18,6 @@ ECHO_LEX = @echo " LEX $@";
> ECHO_AR = @echo " AR $@";
> ECHO_RANLIB = @echo " RANLIB $@";
> SILENCE = @
> +# Silence libtool.
> +SILENT_FLAG = --silent
> endif
Oops, I had not noticed that during review. LGTM:
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
prev parent reply other threads:[~2022-11-07 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 18:13 Tom Tromey
2022-11-07 18:16 ` Simon Marchi [this message]
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=5227d2fb-26fa-907f-de4a-3cdcb47ae813@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).