From: Marcus Rosen <mrosen@lsil.com>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: compatible versions of gdb6.1 and binutils?
Date: Tue, 20 Apr 2004 21:23:00 -0000 [thread overview]
Message-ID: <10EE351D89AE1F488B426AC91EF6EDAB0120C829@server-1.videolocus.com> (raw)
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.
Any help would be much appreciated,
Marcus
next reply other threads:[~2004-04-20 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 21:23 Marcus Rosen [this message]
2004-04-20 22:33 ` Daniel Jacobowitz
2004-04-21 16:40 Marcus Rosen
2004-04-21 18:43 ` '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=10EE351D89AE1F488B426AC91EF6EDAB0120C829@server-1.videolocus.com \
--to=mrosen@lsil.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