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: common: remove unused include paths Date: Thu, 3 Nov 2022 08:20:54 +0000 (GMT) [thread overview] Message-ID: <20221103082054.61F993858D20@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ca7b34c5bead0acd3c93670d849081da04f5bcd9 commit ca7b34c5bead0acd3c93670d849081da04f5bcd9 Author: Mike Frysinger <vapier@gentoo.org> Date: Mon Oct 31 18:16:14 2022 +0545 sim: common: remove unused include paths A bunch of these paths don't include any headers, and most likely never will, so there's no real need to keep them. This will let us harmonize paths with the top-level Makefile more easily, which will in turn make it easier to move more compile steps there. Diff: --- sim/common/Make-common.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sim/common/Make-common.in b/sim/common/Make-common.in index b07ec96e147..094f7412b23 100644 --- a/sim/common/Make-common.in +++ b/sim/common/Make-common.in @@ -206,10 +206,10 @@ CONFIG_CFLAGS = \ $(SIM_WARN_CFLAGS) \ $(SIM_WERROR_CFLAGS) \ $(SIM_HARDWARE) -CSEARCH = -I. -I$(srcdir) -I../common -I$(srccom) \ - -I../../include -I$(srcroot)/include \ +CSEARCH = -I. -I$(srcdir) -I$(srccom) \ + -I$(srcroot)/include \ -I../../bfd -I$(srcroot)/bfd \ - -I../../opcodes -I$(srcroot)/opcodes \ + -I$(srcroot)/opcodes \ -I../.. \ $(INTL_CFLAGS) ALL_CFLAGS = $(CONFIG_CFLAGS) $(CSEARCH) $(INCGNU) $(SIM_EXTRA_CFLAGS) $(CFLAGS)
reply other threads:[~2022-11-03 8:20 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=20221103082054.61F993858D20@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: linkBe 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).