From: Daniel Jacobowitz <drow@mvista.com>
To: GDB list <gdb@sources.redhat.com>
Subject: Re: Binutils and GDB
Date: Thu, 07 Aug 2003 13:52:00 -0000 [thread overview]
Message-ID: <20030807135228.GB28000@nevyn.them.org> (raw)
In-Reply-To: <1060253680.9735.28.camel@steve.softier.local>
On Thu, Aug 07, 2003 at 01:54:39PM +0300, Stephen Biggs wrote:
> On Wed, 2003-08-06 at 15:53, Daniel Jacobowitz wrote:
> > On Wed, Aug 06, 2003 at 03:05:27PM +0300, Stephen Biggs wrote:
> > > Greetings all,
> > >
> > > I apologize for what will probably seem a hopelessly clueless and newbie
> > > question, but I am stuck, so here goes:
> > >
> > > I notice that the GDB source tree has a lot of what seems to be almost
> > > identical code in common with the binutils source tree. I have made
> > > some changes to the binutils 2.14 source tree, specifically in the BFD
> > > and opcodes directories that I wish to integrate into GDB. How do I do
> > > this with the minimum amount of effort? Is there a way to tell the GDB
> > > configure to not configure the GDB's bfd, rather use another already
> > > built BFD library? How, if so?
> >
> > No, GDB can't use the system BFD. I recommend just applying the patch.
> > The directory is common to both projects, but gdb and binutils branch
> > at different times.
> >
> But, this is a big mess, no? That means that any changes in the system
> binutils BFD have to be reflected in the GDB BFD and back-patched, which
> they seem NOT to be... how does this work at all?
Eh?
The master sources for binutils and GDB live in the same CVS
repository. So the masters are always in sync. Distributors have to
patch both copies if they need local patches - but in general, they
don't.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-07 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 12:05 Stephen Biggs
2003-08-06 12:54 ` Daniel Jacobowitz
2003-08-07 10:54 ` Stephen Biggs
2003-08-07 13:52 ` Daniel Jacobowitz [this message]
2003-08-10 9:36 ` Stephen Biggs
2003-08-13 23:53 ` Daniel Jacobowitz
2003-08-14 10:04 ` Stephen Biggs
2003-08-14 14:20 ` Daniel Jacobowitz
2003-08-17 7:48 ` Stephen Biggs
2003-08-17 14:21 ` Daniel Jacobowitz
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=20030807135228.GB28000@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).