From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] sim: common: drop libcommon.a linkage
Date: Mon, 2 Jan 2023 22:21:52 -0500 [thread overview]
Message-ID: <20230103032152.24238-1-vapier@gentoo.org> (raw)
All of these objects should be in libsim.a already, so don't link to
it too. In practice it never gets used, but no point in listing it.
---
sim/Makefile.in | 7 ++-----
sim/common/local.mk | 4 +---
2 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/sim/common/local.mk b/sim/common/local.mk
index 22917e0f8a64..dd6ed5fec83c 100644
--- a/sim/common/local.mk
+++ b/sim/common/local.mk
@@ -30,8 +30,7 @@ SIM_ALL_RECURSIVE_DEPS += \
## NB: libcommon.a isn't used directly by ports. We need a target for common
## objects to be a part of, and ports use the individual objects directly.
-SIM_COMMON_LIB = %D%/libcommon.a
-noinst_LIBRARIES += $(SIM_COMMON_LIB)
+noinst_LIBRARIES += %D%/libcommon.a
%C%_libcommon_a_SOURCES = \
%D%/callback.c \
%D%/portability.c \
@@ -136,7 +135,6 @@ BFD_LIB = ../bfd/libbfd.la
OPCODES_LIB = ../opcodes/libopcodes.la
SIM_COMMON_LIBS = \
- $(SIM_COMMON_LIB) \
$(BFD_LIB) \
$(OPCODES_LIB) \
$(LIBIBERTY_LIB) \
--
2.39.0
reply other threads:[~2023-01-03 3:21 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=20230103032152.24238-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@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).