Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-embedded
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-embedded@g.o
From: Christopher Friedt <chrisfriedt@...>
Subject: Re: gcc-4.6 / bionic
Date: Thu, 19 May 2011 21:31:43 -0400
I'm almost inclined to think it's an ISA issue, but I guess it's
impossible to know where a SIGILL is coming from until it's run
through gdb.

I don't actually have gdb up and running yet, unfortunately, but
that's the route I would take. I believe they both use a version of
libiberty that needs to be patched, and I could probably recycle some
of the same patches I used for gcc-4.6.

I'll keep you informed.

C

On Thu, May 19, 2011 at 1:49 PM, Peter Stuge <peter@...> wrote:
> Christopher Friedt wrote:
>> I just set up a new vmware image runing gentoo (i686) and didn't run
>> into any of the illegal instruction issues that you mentioned.
>
> I'll send you my kernel. I ran on a Thinkpad X40, Pentium-M.
>
>
> //Peter
>
>


Replies:
Re: gcc-4.6 / bionic
-- Christopher Friedt
References:
Re: gcc-4.6 / bionic
-- Christopher Friedt
Re: gcc-4.6 / bionic
-- Mike Frysinger
Re: gcc-4.6 / bionic
-- Christopher Friedt
Re: gcc-4.6 / bionic
-- Ed W
Re: gcc-4.6 / bionic
-- Peter Stuge
Re: gcc-4.6 / bionic
-- Christopher Friedt
Re: gcc-4.6 / bionic
-- Christopher Friedt
Re: gcc-4.6 / bionic
-- Peter Stuge
Re: gcc-4.6 / bionic
-- Christopher Friedt
Re: gcc-4.6 / bionic
-- Peter Stuge
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: gcc-4.6 / bionic
Next by thread:
Re: gcc-4.6 / bionic
Previous by date:
Re: gcc-4.6 / bionic
Next by date:
Re: sys-include symlink?


Updated Jun 25, 2012

Summary: Archive of the gentoo-embedded mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.