From: Fernando Nasser <fnasser@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Nick Clifton <nickc@cambridge.redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: Confusion over the definition of 'bool' in rdi-share/host.h
Date: Wed, 06 Feb 2002 06:13:00 -0000 [thread overview]
Message-ID: <3C6139CC.274DFEA5@redhat.com> (raw)
In-Reply-To: <200202061055.KAA25668@cam-mail2.cambridge.arm.com>
Richard Earnshaw wrote:
>
> > Hi Guys,
> >
> > The ARM port of GDB is currently failing to build for me because of
> > this problem:
> >
> > In file included from /home/nickc/work/sources/egcs/gdb/rdi-share/ardi.h:17,
> > from /home/nickc/work/sources/egcs/gdb/remote-rdi.c:46:
> > /home/nickc/work/sources/egcs/gdb/rdi-share/host.h:123: conflicting types for `_Bool'
> > /usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdbool.h:41: previous declaration of `_Bool'
> >
> > It seems that host.h has code that looks like this (trimmed a little):
> >
> > # define _bool int
> >
> > #ifdef _bool
> > typedef _bool bool;
> > #endif
> >
> > And stdbool.h has:
> >
> > typedef enum
> > {
> > false = 0,
> > true = 1
> > } _Bool;
> >
> > #define bool _Bool
> >
> > So the typedef in host.h becomes, effectively "typedef int enum _Bool".
> >
> > I am not sure if we are allowed to modify rdi-share/host.h, it
> > appears to be copyright to ARM, but if we are, then may I submit the
> > following patch to undefine bool before it is used ?
> >
> > Cheers
> > Nick
>
> the rdi's host.h is really a non-autoconf approach to generating host
> definitions. It's contents should really be replaced with an include of
> the standard autoconf generated definitions followed by some cleanups (ie
> defining the types that the rdi code need in terms of what autoconf has
> provided) to make the rest of the rdi files compile cleanly.
>
> R.
Yes.
But until someone finds the time to do that I guess we must apply
Nick's patch.
Regards to all,
Fernando
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2002-02-06 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 10:11 Nick Clifton
2002-02-05 10:59 ` Daniel Jacobowitz
2002-02-05 11:38 ` Stan Shebs
2002-02-05 19:29 ` Andrew Cagney
2002-02-06 13:02 ` Grant Edwards
2002-02-06 21:36 ` Stan Shebs
2002-02-14 8:09 ` Grant Edwards
2002-02-06 2:57 ` Richard Earnshaw
2002-02-06 6:13 ` Fernando Nasser [this message]
2002-02-06 13:06 ` Grant Edwards
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=3C6139CC.274DFEA5@redhat.com \
--to=fnasser@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@cambridge.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