Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] qt4: remove the option -feliminate-dwarf2-dups to fix the build
Date: Tue, 29 Mar 2011 11:43:30 +0100	[thread overview]
Message-ID: <1301395410.24596.22.camel@rex> (raw)
In-Reply-To: <c9789f2d0873c6b8ff2ae3a7b338b72527cfbf02.1301388474.git.dexuan.cui@intel.com>

On Tue, 2011-03-29 at 16:52 +0800, Dexuan Cui wrote:
> From: Dexuan Cui <dexuan.cui@intel.com>
> 
> [YOCTO #932]
> 
> After commit 5ea06dc295b657383fd97545c15255b294cf1a79(bitbake.conf: Prune
> global OPTIMIZATION flags) that adds an option -feliminate-dwarf2-dups,
> gcc 4.5 reports such an internal compiler error when building Qt4 if the
> option is used:
> 
> | graphicsview/qgridlayoutengine.cpp:1553:1: internal compiler error: in build_abbrev_table, at dwarf2out.c:9806
> | Please submit a full bug report,
> | with preprocessed source if appropriate.
> | See <http://gcc.gnu.org/bugs.html> for instructions.
> 
> This is a gcc bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47361
> 
> At present we can remove the option as a workaround.
> 
> Thanks Robert Berger for reporting the bug and his investigation in gcc
> bugzilla and thanks Khem Raj for the quick suggestion about removing
> the option.

How about we add the patch for this issue:

http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01647.html

?

Cheers,

Richard




  reply	other threads:[~2011-03-29 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  8:52 [PATCH 0/1] qt4: remove the option -feliminate-dwarf2-dups to fix the build Dexuan Cui
2011-03-29  8:52 ` [PATCH 1/1] " Dexuan Cui
2011-03-29 10:43   ` Richard Purdie [this message]
2011-03-29 11:43     ` Cui, Dexuan
2011-04-08 18:18       ` [poky] " Saul Wold
2011-04-08 18:32         ` Gary Thomas
2011-04-09 13:48         ` Cui, Dexuan

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=1301395410.24596.22.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox