From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, "Martin M. Hunt" <hunt@redhat.com>
Subject: Re: [RFA] fix for utils.c bool problem
Date: Fri, 08 Feb 2002 09:09:00 -0000 [thread overview]
Message-ID: <3C640642.3020908@cygnus.com> (raw)
In-Reply-To: <20020208115715.A21971@nevyn.them.org>
>
> Sorry if I missed an objection. I was a little out of it yesterday.
>
> The immediate problem was -not- fixed. To start back at the beginning
> again:
> - On my machine, running a current Debian system, <curses.h> includes
> <stdbool.h>. We have to live with that. There's nothing I can
> particularly do about it.
Is that a current or a released debian system? A released system I'd
probably agreeable to. A current system I'm less so.
> - The way I tried to fix this was by also using stdbool.h if it was
> available. But <stdbool.h> conflicts with an awful lot of existing
> code. This is unfortunate, and this is where the proper fix lies,
> IMO.
> - The way I settled on fixing this, and committed, was to use
> <stdbool.h> if something included before bfd.h had already brought
> it in. This appears to work in all cases.
>
> I strongly want to avoid leaving GDB unbuildable on this class of
> systems. I don't have any particular attachment to my patch. I would
> love to revert it, as soon as there is an alternative solution in
> place.
See my thread on binutils about how to fix the problem.
enjoy,
Andrew
next prev parent reply other threads:[~2002-02-08 17:09 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
2002-02-08 8:51 ` Andrew Cagney
2002-02-08 8:57 ` Daniel Jacobowitz
2002-02-08 9:09 ` Andrew Cagney [this message]
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=3C640642.3020908@cygnus.com \
--to=ac131313@cygnus.com \
--cc=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