From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/2] sim: rename BUILD_LDFLAGS to LDFLAGS_FOR_BUILD
Date: Mon, 8 Mar 2021 03:22:53 -0500 [thread overview]
Message-ID: <20210308082253.9975-2-vapier@gentoo.org> (raw)
In-Reply-To: <20210308082253.9975-1-vapier@gentoo.org>
The rest of the binutils tree renamed this variable many years ago.
---
sim/common/Make-common.in | 2 +-
sim/igen/Makefile.in | 4 ++--
sim/igen/configure | 4 ++++
sim/igen/configure.ac | 3 +++
sim/ppc/Makefile.in | 4 ++--
5 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/sim/common/Make-common.in b/sim/common/Make-common.in
index 8b35deb51679..f4a7e8da11de 100644
--- a/sim/common/Make-common.in
+++ b/sim/common/Make-common.in
@@ -249,7 +249,7 @@ EXTRA_LIBS = $(BFD_LIB) $(OPCODES_LIB) $(LIBINTL) $(LIBIBERTY_LIB) \
LIB_OBJS = callback.o syscall.o targ-map.o version.o $(SIM_OBJS)
COMPILE_FOR_BUILD = $(CC_FOR_BUILD) $(BUILD_CFLAGS)
-LINK_FOR_BUILD = $(CC_FOR_BUILD) $(BUILD_CFLAGS) $(BUILD_LDFLAGS) -o $@
+LINK_FOR_BUILD = $(CC_FOR_BUILD) $(BUILD_CFLAGS) $(LDFLAGS_FOR_BUILD) -o $@
RUNTESTFLAGS =
diff --git a/sim/igen/Makefile.in b/sim/igen/Makefile.in
index 60626adafc31..3c06c724ee81 100644
--- a/sim/igen/Makefile.in
+++ b/sim/igen/Makefile.in
@@ -60,6 +60,7 @@ CFLAGS = @CFLAGS@
CC_FOR_BUILD = @CC_FOR_BUILD@
CFLAGS_FOR_BUILD = @CFLAGS_FOR_BUILD@
+LDFLAGS_FOR_BUILD = @LDFLAGS_FOR_BUILD@
WARN_CFLAGS = @WARN_CFLAGS@
WERROR_CFLAGS = @WERROR_CFLAGS@
@@ -80,10 +81,9 @@ BUILD_CFLAGS = \
$(IGEN_WARN_CFLAGS) \
$(IGEN_WERROR_CFLAGS) \
$(INCLUDES)
-BUILD_LDFLAGS =
COMPILE_FOR_BUILD = $(CC_FOR_BUILD) $(BUILD_CFLAGS)
-LINK_FOR_BUILD = $(CC_FOR_BUILD) $(CFLAGS_FOR_BUILD) $(BUILD_LDFLAGS) -o $@
+LINK_FOR_BUILD = $(CC_FOR_BUILD) $(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD) -o $@
all: igen
#all: tmp-filter tmp-table tmp-ld-insn tmp-ld-cache tmp-ld-decode tmp-gen
diff --git a/sim/igen/configure.ac b/sim/igen/configure.ac
index 807e1d596939..d87673e90563 100644
--- a/sim/igen/configure.ac
+++ b/sim/igen/configure.ac
@@ -11,14 +11,17 @@ SIM_AC_OPTION_WARNINGS
if test "x$cross_compiling" = "xno" -a "x$host" != "xi386-windows"; then
CC_FOR_BUILD='$(CC)'
CFLAGS_FOR_BUILD='$(CFLAGS)'
+ LDFLAGS_FOR_BUILD='$(LDFLAGS)'
else
CC_FOR_BUILD=${CC_FOR_BUILD-gcc}
CFLAGS_FOR_BUILD=${CFLAGS_FOR_BUILD-"-g"}
+ LDFLAGS_FOR_BUILD=
fi
AC_CANONICAL_SYSTEM
AC_SUBST(CC_FOR_BUILD)
AC_SUBST(CFLAGS_FOR_BUILD)
+AC_SUBST(LDFLAGS_FOR_BUILD)
AC_OUTPUT(Makefile)
diff --git a/sim/ppc/Makefile.in b/sim/ppc/Makefile.in
index 8c586350b9dc..ae99dc3a1038 100644
--- a/sim/ppc/Makefile.in
+++ b/sim/ppc/Makefile.in
@@ -107,11 +107,11 @@ STD_CFLAGS = $(CFLAGS) $(INLINE_CFLAGS) $(CONFIG_CFLAGS) $(WARNING_CFLAGS) $(INC
NOWARN_CFLAGS = $(CFLAGS) $(INLINE_CFLAGS) $(CONFIG_CFLAGS) $(INCLUDES) $(SIM_FPU_CFLAGS)
BUILD_CFLAGS = $(CFLAGS_FOR_BUILD) $(INCLUDES) $(WARNING_CFLAGS)
-BUILD_LDFLAGS =
+LDFLAGS_FOR_BUILD =
LIBS = @LIBS@
COMPILE_FOR_BUILD = $(CC_FOR_BUILD) $(BUILD_CFLAGS)
-LINK_FOR_BUILD = $(CC_FOR_BUILD) $(BUILD_CFLAGS) $(BUILD_LDFLAGS) -o $@
+LINK_FOR_BUILD = $(CC_FOR_BUILD) $(BUILD_CFLAGS) $(LDFLAGS_FOR_BUILD) -o $@
CONFIG_FILE = @sim_config@
IGEN_OPCODE_RULES = @sim_opcode@
--
2.30.0
prev parent reply other threads:[~2021-03-08 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 8:22 [PATCH 1/2] sim: introduce {COMPILE,LINK}_FOR_BUILD Mike Frysinger
2021-03-08 8:22 ` Mike Frysinger [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=20210308082253.9975-2-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).