From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/commit 1/3] language.h: Add "symtab.h" #include
Date: Mon, 11 Nov 2013 06:38:00 -0000 [thread overview]
Message-ID: <1384151855-12926-1-git-send-email-brobecker@adacore.com> (raw)
Hello,
I noticed this when I tried to #include "language.h" from mi-parse.c,
when I got compilation errors from missing type declarations:
In addition to the fact that language.h depends on a number of struct
types declared in symtab.h, language.h also depends on an enumerated
type (domain_enum). So language.h should #include "symtab.h".
gdb/ChangeLog:
* language.h: Add "symtab.h" #include.
Tested on x86_64-linux. I think this patch should go in on its own.
---
gdb/language.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdb/language.h b/gdb/language.h
index 5e029ea..d730bf5 100644
--- a/gdb/language.h
+++ b/gdb/language.h
@@ -23,6 +23,8 @@
#if !defined (LANGUAGE_H)
#define LANGUAGE_H 1
+#include "symtab.h"
+
/* Forward decls for prototypes. */
struct value;
struct objfile;
--
1.8.1.2
next reply other threads:[~2013-11-11 6:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 6:38 Joel Brobecker [this message]
2013-11-11 6:39 ` [RFA 2/3] New function cli-utils.c:extract_arg_const Joel Brobecker
2013-11-13 19:35 ` Pedro Alves
2013-11-14 10:55 ` pushed: " Joel Brobecker
2013-11-11 6:55 ` [RFC 3/3] GDB/MI: Add new "--language LANG" command option Joel Brobecker
2013-11-11 7:02 ` Joel Brobecker
2013-11-11 17:20 ` Eli Zaretskii
2013-11-11 16:29 ` Eli Zaretskii
2013-11-13 19:49 ` Pedro Alves
2013-11-14 11:17 ` Joel Brobecker
2013-11-13 19:34 ` [PATCH] New "make check-headers" rule. (was: Re: [RFA/commit 1/3] language.h: Add "symtab.h" #include) Pedro Alves
2013-11-14 10:00 ` Joel Brobecker
2013-11-14 21:32 ` [PATCH] New "make check-headers" rule Tom Tromey
2014-01-13 19:42 ` Pedro Alves
2013-11-14 10:55 ` pushed: [RFA/commit 1/3] language.h: Add "symtab.h" #include Joel Brobecker
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=1384151855-12926-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.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).