public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Silence libtool during link
Date: Mon,  7 Nov 2022 19:54:49 +0000 (GMT)	[thread overview]
Message-ID: <20221107195449.C989E3858C56@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=027fb74964e6e86d666bc7b15e072206f684ddf2

commit 027fb74964e6e86d666bc7b15e072206f684ddf2
Author: Tom Tromey <tromey@adacore.com>
Date:   Mon Nov 7 10:43:25 2022 -0700

    Silence libtool during link
    
    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.
    
    Approved-By: Simon Marchi <simon.marchi@efficios.com>

Diff:
---
 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

                 reply	other threads:[~2022-11-07 19:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221107195449.C989E3858C56@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).