public inbox for
 help / color / mirror / Atom feed
From: Keith Seitz <>
To: Brian Phillips <>
Subject: Re: update to insight?
Date: Sun, 10 Feb 2013 16:56:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1360463415.2414.8.camel@golden>

On 02/09/2013 06:30 PM, Brian Phillips wrote:

> Are there any plans to continue updating 'insight'?

Insight is largely in maintenance mode. I still use it daily, and I will 
continue to do whatever I need to do to keep it working.

> It would be great to have a source that will compile with gcc >= 4.7.x.
> As a new linux user, I don't know how to install / use gcc 4.2 alongside
> 4.7 on my system - and if I understand correctly, from comments found
> online, 4.2 is required for compiling?  (I tried --disable-werror in
> the ../src/configure command, but that didn't work).

I build on Fedora 15, 17, Ubuntu 12.10, and Windows/MinGW fairly 
regularly. Fedora 17 comes with GCC 4.7.2, and I have no problems 
building for x86_64.

> I always get this error.
> linux-nat.h:63:18: error: field ‘siginfo’ has incomplete type
> make[2]: *** [i386-linux-nat.o] Error 1
> If you would like more information from me, I'm happy to provide what I
> can - just tell me what to do! :)

First things first. What is your configure triple? Can you configure and 
build gdb without Insight? What version of insight are you trying to build?

FWIW, I use CVS HEAD. I've never used a release, and I haven't made one 
in years. Now that things are starting to settle down around me, I am 
hoping to commit a few important patches for x86_64 and MinGW and make a 
new release. 6.8 is (obviously) ancient.

I've never tried Arch linux, but I'll try installing it into a VM...


  reply	other threads:[~2013-02-10 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  2:30 Brian Phillips
2013-02-10 16:56 ` Keith Seitz [this message]
2013-02-10 19:57   ` Alessandro Salvatori
2013-02-10 22:56   ` Brian Phillips
2013-02-21  3:11     ` Keith Seitz

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