All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Subject: Re: internal compiler error with qt building poky-image-lsb-sdk
Date: Sun, 27 Mar 2011 15:21:58 +0300	[thread overview]
Message-ID: <imna56$d09$1@dough.gmane.org> (raw)
In-Reply-To: <20110327053222.GA22396@sakrah.homelinux.org>

Hi Khem,

On 03/27/2011 08:32 AM, Khem Raj wrote:
> On (26/03/11 17:53), Robert Berger wrote:
>> Hi,
>>
>> The short version:
>>
>> With commit f8539239bc473279cc475b07c22e1e96514c6d2f Thu Mar 24 13:03:50
>> 2011 +0000 both beagleboard and routerstationpro fail to build due to an
>> internal compiler error:
>>
>> ../../include/QtCore/../../src/corelib/tools/qstring.h:187:17: note: the
>> mangling of 'va_list' has changed in GCC 4.4
>> graphicsview/qgridlayoutengine.cpp:1553:1: internal compiler error: in
>> build_abbrev_table, at dwarf2out.c:9806
> 
> Can you try after addding the following to the failing recipe with 
> 
> CXXFLAGS := "${@oe_filter_out('-feliminate-dwarf2-dups', '${CXXFLAGS}',
> d)}"

I'm sorry I can't try right now, since I'm out of office for a week and
training people in Embedded Linux ;)

I can give it a try earliest in the week of 3rd of April.

Maybe someone else could try in the meantime. It's really easy to reproduce.
*) Just check out the latest from git
*) build poky-image-lsb-sdk for beagleboard

... and wait some hours ...

Regards,

Robert

> 
> -Khem

..."At Group L, Stoffel oversees six first-rate programmers, a
managerial challenge roughly comparable to herding cats." - The
Washington Post Magazine, June 9, 1985

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




      reply	other threads:[~2011-03-27 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 15:53 internal compiler error with qt building poky-image-lsb-sdk Robert Berger
2011-03-27  5:32 ` Khem Raj
2011-03-27 12:21   ` Robert Berger [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:
  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='imna56$d09$1@dough.gmane.org' \
    --to=gmane@reliableembeddedsystems.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.