Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ml@communistcode.co.uk
Cc: openembedded-core@lists.openembedded.org
Subject: Re: gcc compile error
Date: Tue, 16 Apr 2013 09:17:14 +0100	[thread overview]
Message-ID: <1366100234.8670.86.camel@ted> (raw)
In-Reply-To: <516D0783.8040608@communistcode.co.uk>

On Tue, 2013-04-16 at 09:10 +0100, Jack Mitchell wrote:
> On 16/04/13 05:38, Yi Qingliang wrote:
> > hello, i'm using archlinux, the gcc is 4.8.0.
> >
> > when compiling gcc 4.7.2 in oe, I got the error:
> >
> > | /mnt/src/arm9plf-build/tmp/work-shared/gcc-4.7.2-
> > r19/gcc-4.7.2/libgcc/libgcc2.c: In function '__absvdi2':
> > | /mnt/src/arm9plf-build/tmp/work-shared/gcc-4.7.2-
> > r19/gcc-4.7.2/libgcc/libgcc2.c:273:1: internal compiler error: Segmentation
> > fault
> >
> >
> >
> 
> Hi,
> 
> Many people have run into this problem so far (myself included) and I 
> have been told it is the fault of the ArchLinux GCC. Now, I noticed the 
> ArchLinux devs pushed a new build of GCC out yesterday, have you tried 
> upgrading to that yet and giving it another go?
> 
> If not, my solution was to move to GCC 4.8 using the patches posted to 
> oe-core/oe-dev.

We're a bit stuck on this one since the host gcc is segfaulting. This is
very clearly something the host gcc should not do and there is little we
can do to fix it. The gcc 4.8 codebase doesn't trigger the fault, only
the earlier ones like 4.7.

There is an open bug:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4248

Cheers,

Richard





  reply	other threads:[~2013-04-16  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  4:38 gcc compile error Yi Qingliang
2013-04-16  8:10 ` Jack Mitchell
2013-04-16  8:17   ` Richard Purdie [this message]
2013-04-17  1:56   ` Yi Qingliang
2013-04-17  2:21     ` Khem Raj

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1366100234.8670.86.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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