From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: "Martin M. Hunt" <hunt@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] fix for utils.c bool problem
Date: Thu, 07 Feb 2002 15:28:00 -0000 [thread overview]
Message-ID: <3C630D85.2090601@cygnus.com> (raw)
In-Reply-To: <20020207171414.A5630@nevyn.them.org>
> but the ``I think'' highlights the problem :-( I don't think we should
>> be working around problems in an un released BFD :-/
>
>
> I don't follow that. If we ever, ever built using a "system" bfd.h,
> maybe. BFD is part of our source distribution, for all that it is
> owned by a different group. "Released" doesn't mean anything.
BFD and GDB share a common repository as this allows close co-operation.
If it were possible, we'd be sharing a repository with GCC. These GDB
vs BFD problems come up all the time (this one is just extra nasty :-).
I think both GDB and BINUTILS should be getting together and fixing
the problem. Obviously if this had come up after a branch had been cut,
I'd likely be giving a very different story - HACK - fortunatly it didn't.
> The names that would need to be changed are 'true' and 'false'. That's
> a problem of fairly great magnitude.
While the problem is going to cause much entropy in the code, it should
also be 100% mechanical. Look at other changes that have gone through
GDB they were far less mechanical but still successful.
As they say, GDB can provide BINUTILS with the necessary technical
knowledge :-^
enjoy,
Andrew
next prev parent reply other threads:[~2002-02-07 23:28 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 [this message]
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=3C630D85.2090601@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