From: Keith Seitz <keiths@redhat.com>
To: Lisa McIlrath <lmcilrath@r3logic.com>
Cc: insight@sourceware.org
Subject: Re: updated gdb source
Date: Wed, 21 Aug 2013 04:14:00 -0000 [thread overview]
Message-ID: <52143E8A.7040508@redhat.com> (raw)
In-Reply-To: <52143BAB.9060401@r3logic.com>
On 08/20/2013 09:01 PM, Lisa McIlrath wrote:
> Is there any way to get an updated source version with fresh gdb code
> that will build?
Two options here -- one available now, one in the coming weeks:
1) (available now) Use CVS/GIT head. This is what I use. I build every
other week or so. In a similar vein, grab the sources for a release and
the insight sources from the same time. I believe Kevin Buettner tagged
insight for the last gdb release, so you can probably just checkout the
"insight" module on the last release branch.
2) (available soon) Checkout the insight GIT repository and add gdb as a
remote git repository. Sourecware overseers just set this up for me, but
I'm on vacation for most of the week so I won't get to checking in
initial branches and testing until next week at the earliest.
Keith
next prev parent reply other threads:[~2013-08-21 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 4:01 Lisa McIlrath
2013-08-21 4:14 ` Keith Seitz [this message]
2013-08-21 14:07 ` Lisa McIlrath
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=52143E8A.7040508@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=lmcilrath@r3logic.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).