From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Fix ARM simulator build on Windows
Date: Thu, 9 Dec 2021 07:02:12 -0700 [thread overview]
Message-ID: <20211209140212.3980587-1-tromey@adacore.com> (raw)
For a Windows-hosted build with arm-elf as the target, the sim build
fails like:
[...]sim-io.c:214:29: error: 'struct host_callback_struct' has no member named 'open'
The recent header reorganization seems to have caused this, because
now 'open' is redefined by the gnulib fcntl.h.
The fix is simple: remove the undef of 'open' from sim-io.c.
---
sim/common/sim-io.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/sim/common/sim-io.c b/sim/common/sim-io.c
index 8c40f7a0e73..8cc078c3cd2 100644
--- a/sim/common/sim-io.c
+++ b/sim/common/sim-io.c
@@ -37,8 +37,6 @@
#include "sim-io.h"
#include "sim/callback.h"
-#undef open
-
/* Define the rate at which the simulator should poll the host
for a quit. */
#ifndef POLL_QUIT_INTERVAL
--
2.31.1
next reply other threads:[~2021-12-09 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 14:02 Tom Tromey via Gdb-patches [this message]
2021-12-10 2:25 ` Mike Frysinger via Gdb-patches
2021-12-16 14:58 ` Tom Tromey via Gdb-patches
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=20211209140212.3980587-1-tromey@adacore.com \
--to=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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