RE: compatible versions of gdb6.1 and binutils?

[Marcus Rosen <mrosen@lsil.com>]

I can see that I would need to checkout the sources from cvs myself.  But my
confusion has to do with how to pick what versions to grab.  I expect that I
would want to grab the gdb alias module at the 6.1 release tag.  But now I'm
not sure how to pick which versions of the naked-ld, naked-gas and
naked-binutils to grab.  Grabbing from the head doesn't seem like an option
since I need to have code that is at least thought to be stable and it would
be nearly impossible for me to upgrade my versions of the sources later if I
couldn't generate diffs against a tag.  What I was hoping was that gdb
depended on a specific "release" of the shared components so that it would
be possible to pick a common baseline between gdb and binutils.  So I'm
wondering if anyone can suggest how I would go about picking these versions,
that is unless I got something completely wrong?

Marcus

-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org]
Sent: Tuesday, April 20, 2004 5:23 PM
To: Marcus Rosen
Cc: 'gdb@sources.redhat.com'
Subject: Re: compatible versions of gdb6.1 and binutils?


On Tue, Apr 20, 2004 at 05:21:10PM -0400, Marcus Rosen wrote:
> Hey,
> 
> I am working on integrating a simulator for a custom sparc into gdb6.1.
> I would like to have the source for gdb and binutils in the same source
tree
> but from what I can tell there is no evidence of any kind of common tags
> across these projects that would indicate how best to merge them.  Is
there
> any kind of common baseline for the shared components (bfd,opcodes,etc)
that
> I should be aiming for? or is my only option to grab what I can tagged at
> the gdb6.1 release and merge in some appropriate binutils directories and
> hope to get them to build?
> 
> My motivation is to avoid replication of the shared components and to be
> able to easily sync my copies with newer releases should it become
> necessary.   

If you want to do this your best bet will be to take a snapshot from
the combined CVS tree rather than using release tarballs.  Otherwise,
combining them is quite difficult, because all the shared directories
evolve.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer