public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Bruce Dawson <bruced@valvesoftware.com>
To: 'Keith Seitz' <keiths@redhat.com>
Cc: "insight@sourceware.org" <insight@sourceware.org>
Subject: RE: Building Insight
Date: Thu, 07 Feb 2013 21:36:00 -0000	[thread overview]
Message-ID: <2AC155A009400B4C8B05D518E4819AEF0718FA46@exchange10.valvesoftware.com> (raw)
In-Reply-To: <511419CF.3010306@redhat.com>

I'll try getting the source from cvs and see if that works. It might be worth putting a mention on the download page that this is recommended, since the current text at http://www.sourceware.org/insight/downloads.php seems to slightly discourage getting the development version.

Thanks for the reply.

-----Original Message-----
From: Keith Seitz [mailto:keiths@redhat.com] 
Sent: Thursday, February 07, 2013 1:17 PM
To: Bruce Dawson
Cc: insight@sourceware.org
Subject: Re: Building Insight

On 02/07/2013 12:06 PM, Bruce Dawson wrote:
> Does insight currently build and work? It appears that it hasn't been 
> updated since July 19, 2009
> (http://www.sourceware.org/insight/news.php) so I'm naturally curious 
> as to whether this project is dead or not.

Insight does build on linux. I build CVS HEAD on Fedora almost daily, and I test Ubuntu about quarterly. It is entirely my fault that the project has been largely in maintenance mode for many years. There just aren't a whole lot of contributors anymore.

First things first -- get rid of 6.8. I simply haven't made an official release in quite some time. I see that despite my intentions, another GDB release occurs where I haven't made a corresponding insight release.

To further complicate matters, I have been sitting on x86_64 and mingw build fixes for a long time...

Here's what I would do. If you don't mind using a development version of GDB (which is what I have been using daily for many years), grab the latest sources of the insight CVS module from anonymous CVS.

If you would prefer using a standard release of GDB, grab those sources and then add in the missing insight bits from CVS.

If worse comes to worse, ping me privately, and I'll attempt to through you together an unofficial source tarball that I have built on Ubuntu myself. [This might be easier/less frustrating, considering I have all the necessary bits for x86_64 lying in my source tree.]

I will redouble my efforts to get all my cord-hoarding checked into sourceware.org and make an official release after the 7.6 is underway. 
That should be branching within the next week or two.

Keith

  reply	other threads:[~2013-02-07 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 20:07 Bruce Dawson
2013-02-07 21:17 ` Keith Seitz
2013-02-07 21:36   ` Bruce Dawson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-30 12:42 Syd Polk
2000-06-22  3:26 Cor van Loos

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=2AC155A009400B4C8B05D518E4819AEF0718FA46@exchange10.valvesoftware.com \
    --to=bruced@valvesoftware.com \
    --cc=insight@sourceware.org \
    --cc=keiths@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).