From: "Martin M. Hunt" <hunt@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] fix for utils.c bool problem
Date: Thu, 07 Feb 2002 13:33:00 -0000 [thread overview]
Message-ID: <200202072133.NAA28346@cygnus.com> (raw)
Am I the only one seeing this? On three different build systems I am getting errors like
gcc -c -g -O2 -I/usr/include/v9 -I. -I../../src/gdb -I../../src/gdb/config -DHAVE_CONFIG_H -I../../src/gdb/../include/opcode -I../../src/gdb/../readline/.. -I../bfd -I../../src/gdb/../bfd -I../../src/gdb/../include -I../intl -I../../src/gdb/../intl -DMI_OUT=1 -DGDBTK -DUI_OUT=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized ../../src/gdb/utils.c
In file included from /usr/progressive/lib/gcc-lib/sparc-sun-solaris2.5/2.96-gnupro-00r1/include/curses.h:5,
from ../../src/gdb/utils.c:30:
/usr/include/curses.h:69: conflicting types for `_Bool'
/usr/progressive/lib/gcc-lib/sparc-sun-solaris2.5/2.96-gnupro-00r1/include/stdbool.h:41: previous declaration of `_Bool'
Some newer versions of gcc apparently have stdbool.h improvements that
fix the problem. Another fix is to simply reorder the patch, which fixes builds
on all of my systems (Windows, Linux, Solaris)
--
Martin Hunt
GDB Engineer
Red Hat, Inc.
2002-02-07 Martin M. Hunt <hunt@redhat.com>
* utils.c: Reorder includes to eliminate bool conflict.
Index: utils.c
===================================================================
RCS file: /cvs/src/src/gdb/utils.c,v
retrieving revision 1.61
diff -u -p -r1.61 utils.c
--- utils.c 2002/02/05 04:37:22 1.61
+++ utils.c 2002/02/07 21:32:35
@@ -20,18 +20,18 @@
Foundation, Inc., 59 Temple Place - Suite 330,
Boston, MA 02111-1307, USA. */
-#include "defs.h"
-#include "gdb_assert.h"
-#include <ctype.h>
-#include "gdb_string.h"
-#include "event-top.h"
-
#ifdef HAVE_CURSES_H
#include <curses.h>
#endif
#ifdef HAVE_TERM_H
#include <term.h>
#endif
+
+#include "defs.h"
+#include "gdb_assert.h"
+#include <ctype.h>
+#include "gdb_string.h"
+#include "event-top.h"
#ifdef __GO32__
#include <pc.h>
next reply other threads:[~2002-02-07 21:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 13:33 Martin M. Hunt [this message]
2002-02-07 13:39 ` Daniel Jacobowitz
2002-02-07 14:01 ` Andrew Cagney
2002-02-07 14:14 ` Daniel Jacobowitz
2002-02-07 15:28 ` Andrew Cagney
2002-02-08 7:57 ` Daniel Jacobowitz
2002-02-08 8:51 ` Andrew Cagney
2002-02-08 8:57 ` Daniel Jacobowitz
2002-02-08 9:09 ` Andrew Cagney
2002-02-08 9:38 ` Daniel Jacobowitz
2002-02-08 10:55 ` Andrew Cagney
2002-02-28 22:04 ` Andrew Cagney
2002-02-07 13:40 ` Fernando Nasser
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=200202072133.NAA28346@cygnus.com \
--to=hunt@redhat.com \
--cc=gdb-patches@sources.redhat.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