Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: "Martin M. Hunt" <hunt@redhat.com>
Subject: Re: [RFA] fix for utils.c bool problem
Date: Fri, 08 Feb 2002 07:57:00 -0000	[thread overview]
Message-ID: <20020208105750.A16802@nevyn.them.org> (raw)
In-Reply-To: <20020207163944.A30605@nevyn.them.org>

On Thu, Feb 07, 2002 at 04:39:44PM -0500, Daniel Jacobowitz wrote:
> On Thu, Feb 07, 2002 at 01:32:53PM -0800, Martin M. Hunt wrote:
> > 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)
> 
> This is the patch I alluded to earlier today on binutils@.  It's not
> quite complete, since TUI is also affected; I've attached mine.  I'm
> quite surprised that this fixes the problem for you without the
> corresponding bfd patch that I haven't committed yet!

No one objected, so I've committed this.  As far as I know GDB should
build everywhere it used to before I started playing with bool, as long
as you update both BFD and GDB.  If I'm wrong, please let me know.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2002-02-08 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 13:33 Martin M. Hunt
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 [this message]
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=20020208105750.A16802@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hunt@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