public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] sim: build: add SIM_HW_CFLAGS to top-level build too
Date: Sat, 5 Nov 2022 03:51:26 +0000 (GMT) [thread overview]
Message-ID: <20221105035126.434D53858437@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bfc96c1039d33b1ed0c8b2e1b6fb3859a693cfe9
commit bfc96c1039d33b1ed0c8b2e1b6fb3859a693cfe9
Author: Mike Frysinger <vapier@gentoo.org>
Date: Sat Nov 5 10:33:37 2022 +0700
sim: build: add SIM_HW_CFLAGS to top-level build too
This matches what we do with targets already.
Diff:
---
sim/Makefile.am | 2 ++
sim/Makefile.in | 7 ++++---
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/sim/Makefile.am b/sim/Makefile.am
index d8730f27698..7ea013ac196 100644
--- a/sim/Makefile.am
+++ b/sim/Makefile.am
@@ -46,10 +46,12 @@ AM_CPPFLAGS = \
-I$(srcroot)/include \
-I../bfd \
-I.. \
+ $(SIM_HW_CFLAGS) \
$(SIM_INLINE)
AM_CPPFLAGS_FOR_BUILD = \
-I$(srcroot)/include \
+ $(SIM_HW_CFLAGS) \
$(SIM_INLINE)
COMPILE_FOR_BUILD = $(CC_FOR_BUILD) $(AM_CPPFLAGS_FOR_BUILD) $(CPPFLAGS_FOR_BUILD) $(CFLAGS_FOR_BUILD)
LINK_FOR_BUILD = $(CC_FOR_BUILD) $(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD) -o $@
diff --git a/sim/Makefile.in b/sim/Makefile.in
index 57c1fc034a0..06d5da1ecf5 100644
--- a/sim/Makefile.in
+++ b/sim/Makefile.in
@@ -924,9 +924,10 @@ MOSTLYCLEANFILES = core $(am__append_5) site-sim-config.exp \
$(am__append_34) $(am__append_37) $(am__append_39)
AM_CFLAGS = $(WERROR_CFLAGS) $(WARN_CFLAGS)
AM_CPPFLAGS = $(INCGNU) -I$(srcroot)/include -I../bfd -I.. \
- $(SIM_INLINE) -I$(srcdir)/common -DSIM_COMMON_BUILD
-AM_CPPFLAGS_FOR_BUILD = -I$(srcroot)/include $(SIM_INLINE) \
- -I$(srcdir)/common
+ $(SIM_HW_CFLAGS) $(SIM_INLINE) -I$(srcdir)/common \
+ -DSIM_COMMON_BUILD
+AM_CPPFLAGS_FOR_BUILD = -I$(srcroot)/include $(SIM_HW_CFLAGS) \
+ $(SIM_INLINE) -I$(srcdir)/common
COMPILE_FOR_BUILD = $(CC_FOR_BUILD) $(AM_CPPFLAGS_FOR_BUILD) $(CPPFLAGS_FOR_BUILD) $(CFLAGS_FOR_BUILD)
LINK_FOR_BUILD = $(CC_FOR_BUILD) $(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD) -o $@
SIM_ALL_RECURSIVE_DEPS = common/libcommon.a $(am__append_2) \
reply other threads:[~2022-11-05 3:51 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=20221105035126.434D53858437@sourceware.org \
--to=vapier@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).