public inbox for
 help / color / mirror / Atom feed
From: Fabio D'Alfonso <>
Subject: Could help with errors building on Ubuntu 15.10?
Date: Wed, 06 Apr 2016 16:30:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

I was trying to build on 15.10 , but I am getting some errors:

I am getting errors on
info-recursive error 1
recipe for all-bfd error 2
recipes for trget all failed error 2

How could I fix?

Thanks for making this big job on Insight!

On 4/6/2016 3:51 PM, Patrick Monnerat wrote:
> On 03/05/2016 05:40 AM, wrote:
>> Hi folks
>> I was going to report this as a bug, but there's a bug in the Insight 
>> bug-reporting system ... :) at least with the link on your Bugs page
>> Anyway. I was trying to install Insight 6.8-1 on Windows 7 32bit, 
>> after first installing Cygwin. I ran into two types of bug, the first 
>> of which I could hack round and the second of which I couldn't:
> I can't help you with I have the same access 
> permissions as you have. Maybe try contacting sourcemaster at 
> sourceware dot org.
> However I see you are trying the latest insight official release, 
> which is very old and outdated: please try git cloning my own version 
> from (in sync with gdb repo < 1 
> week). I've compiled and run it this morning on Linux with success. I 
> succeeded with cygwin and mingw32 on W$ a few months ago. I am not a 
> W$ guy, so the support I can bring for your case is limited.
> It's unofficial but I think this is the most up-to-date you'll find on 
> the net. In any case, you'll have more chance with it that with 6.8.1.
> Good luck,
> Patrick

      reply	other threads:[~2016-04-06 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05  4:40 Windows installation bugs Mark.Bravington
2016-04-06 13:51 ` Patrick Monnerat
2016-04-06 16:30   ` Fabio D'Alfonso [this message]

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