Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: 'Daniel Jacobowitz' <drow@false.org>
To: Marcus Rosen <mrosen@lsil.com>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Re: compatible versions of gdb6.1 and binutils?
Date: Wed, 21 Apr 2004 18:43:00 -0000	[thread overview]
Message-ID: <20040421184243.GA5956@nevyn.them.org> (raw)
In-Reply-To: <10EE351D89AE1F488B426AC91EF6EDAB0120C82A@server-1.videolocus.com>

On Wed, Apr 21, 2004 at 12:06:45PM -0400, Marcus Rosen wrote:
> 
> 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?

There is no depending on specific "releases".  They all live on HEAD;
at one point GDB 6.1 branched; at another point binutils 2.15 branched.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-04-21 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 16:40 Marcus Rosen
2004-04-21 18:43 ` 'Daniel Jacobowitz' [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-20 21:23 Marcus Rosen
2004-04-20 22:33 ` 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=20040421184243.GA5956@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=mrosen@lsil.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