From: Andrew Pinski <apinski@marvell.com>
To: <gdb-patches@sourceware.org>
Cc: Andrew Pinski <apinski@marvell.com>
Subject: [PATCH] Fix compiling of top.c
Date: Wed, 21 Dec 2022 09:41:43 -0800 [thread overview]
Message-ID: <20221221174143.503105-1-apinski@marvell.com> (raw)
When I moved my last patch forward, somehow I missed removing
the #endif for the HAVE_LIBMPFR case.
Committed as obvious after a quick build.
gdb/ChangeLog:
* top.c: Remove the extra #endif which was missed.
---
gdb/top.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/gdb/top.c b/gdb/top.c
index 26e10c7271f..565b455a020 100644
--- a/gdb/top.c
+++ b/gdb/top.c
@@ -1581,7 +1581,6 @@ This GDB was configured as follows:\n\
"));
#endif
-#endif
#if HAVE_LIBXXHASH
gdb_printf (stream, _("\
--with-xxhash\n\
--
2.31.1
reply other threads:[~2022-12-21 17:41 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=20221221174143.503105-1-apinski@marvell.com \
--to=apinski@marvell.com \
--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).