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

On Sun, 2013-02-10 at 08:56 -0800, Keith Seitz wrote:
> 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...
> Keith

Please bear with me - in the past, I've dabbled with C and assembly, but
that was long ago, and I never really had to mess with configuring much
(it was a hobby).  But now, I want to put more effort into learning
assembly (still as a hobby, though).

I don't know what you mean by 'configure triple'.  I'm using a PKGBUILD
at - you can view the
PKGBUILD from the web page, if you like.  If you look there, you might
also look at the comments at the bottom of the page, as well as this
thread, started by me in the forums:

AFAICT, There seems to be a bug in gcc-4.7.2 with a "struct siginfo"
that should be "struct siginfo_t", per this page:

At any rate, other users get stuck with errors like this:
"/home/briphi/builds/gcc46/src/gcc-4.6.3/libgcc/../gcc/config/i386/linux-unwind.h: In function ‘x86_fallback_frame_state’:
/home/briphi/builds/gcc46/src/gcc-4.6.3/libgcc/../gcc/config/i386/linux-unwind.h:138:17: error: field ‘info’ has incomplete type
make[3]: *** [unwind-dw2.o] Error 1"

This applies to me in trying to build older versions of gcc (the snippet
above applies to building gcc-4.6.3) and the same applies to configuring

With my limited knowledge and in using the PKGBUILD at, I'm pretty much stuck to using the source provided in
that script, which is 6.8.1a from  I've tried to monkey
with the source line here, adjusting the first md5sum as needed, but
didn't get any where, due to the linux-unwind.h error above.

I have a dual-boot system with Ubuntu 12.10. Would you mind explaining
what I should do to build from source on Ubuntu?  So far, I've tried
uncompressing the source, and compiling from an alternate directory
using just "../src/configure", but that gave me the following errors:

config.status: creating po/
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
config.status: executing bfd_stdint.h commands
config.status: executing default commands
make[3]: Leaving directory `/home/brian/builds/insight/bfd/po'
make[3]: Entering directory `/home/brian/builds/insight/bfd/po'
make[3]: Nothing to be done for `info'.
make[3]: Leaving directory `/home/brian/builds/insight/bfd/po'
make[3]: Entering directory `/home/brian/builds/insight/bfd'
make[3]: Nothing to be done for `info-am'.
make[3]: Leaving directory `/home/brian/builds/insight/bfd'
make[2]: *** [info-recursive] Error 1
make[2]: Leaving directory `/home/brian/builds/insight/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory `/home/brian/builds/insight'
make: *** [all] Error 2

Here is my gcc --version output from ubuntu:

brian@ubuntumachine:~/builds/insight$ gcc --version
gcc (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2

Many thanks for the reply and being willing to help!

And regarding building gbd, will I be okay doing this in a /home/user
directory?  I don't want to screw up my Ubuntu (or Arch) install, so I'm
a bit hesitant.

Kind regards,

  parent reply	other threads:[~2013-02-10 22: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
2013-02-10 19:57   ` Alessandro Salvatori
2013-02-10 22:56   ` Brian Phillips [this message]
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 \
    --in-reply-to=1360536998.7013.20.camel@ubuwide \ \ \ \

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