public inbox for
 help / color / mirror / Atom feed
From: Bruce Dawson <>
To: "" <>
Subject: Building Insight
Date: Thu, 07 Feb 2013 20:07:00 -0000	[thread overview]
Message-ID: <> (raw)

I'm trying to build Insight so as to have a graphical front-end for GDB on Ubuntu 12.04, gcc 4.6.3. I downloaded the 6.8-1a source (6.8a failed with a texinfo problem) and after adding --disable-werror to the configure command line made some progress on building. That is, I ran these commands:

$ mkdir insight; cd insight
$ ../src/configure --disable-werror
$ make

However I then hit this error:

checking for library containing gethostbyname... none required
checking for library containing socketpair... none required
checking for library containing waddstr... no
checking for library containing dlgetmodinfo... no
checking for library containing tgetent... no
configure: error: no termcap library found
make[1]: *** [configure-gdb] Error 1
make[1]: Leaving directory `/home/bruced/source/insight/insight-6.8-1a/insight'
make: *** [all] Error 2

All of the directions I have found for how to build or install termcap are sufficiently dated that I don't trust them. Is there any advice on how to resolve this problem?

Does insight currently build and work? It appears that it hasn't been updated since July 19, 2009 ( so I'm naturally curious as to whether this project is dead or not.

I definitely find that I am more productive when I can have source/disassembly/call-stack/registers/memory windows open simultaneously and I'm hoping that Insight is the solution for this desire. If there are other options that are being more actively maintained then please let me know.

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 20:07 Bruce Dawson [this message]
2013-02-07 21:17 ` Keith Seitz
2013-02-07 21:36   ` Bruce Dawson
  -- 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).