From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/2] sim: ppc: drop unnecessary config includes
Date: Wed, 8 Sep 2021 21:08:30 -0400 [thread overview]
Message-ID: <20210909010831.13078-1-vapier@gentoo.org> (raw)
This file is compiled for the --host & --build system which leads to
including the configure generated config.h in both environments.
This obviously doesn't work when the two targets don't look alike at
all and can cause build failures here (e.g. a mingw host & a linux
build). Since we don't actually need any config settings in this
very simple file, drop the includes entirely.
---
sim/ppc/filter_filename.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/sim/ppc/filter_filename.c b/sim/ppc/filter_filename.c
index b59ca21ca559..fb2457c0b2c2 100644
--- a/sim/ppc/filter_filename.c
+++ b/sim/ppc/filter_filename.c
@@ -17,10 +17,6 @@
*/
-/* This must come before any other includes. */
-#include "defs.h"
-
-#include "ppc-config.h"
#include "filter_filename.h"
/* Shorten traces by eliminating the directory component to filenames. */
--
2.33.0
next reply other threads:[~2021-09-09 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 1:08 Mike Frysinger [this message]
2021-09-09 1:08 ` [PATCH 2/2] sim: ppc: align format string settings with common code Mike Frysinger
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=20210909010831.13078-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).