Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Peter <ppf83764@freenet.de>
To: openembedded-devel@lists.openembedded.org
Subject: Yocto Dizzy + Beaglebone + Qt5 (Internal compiler error)
Date: Thu, 09 Apr 2015 12:28:47 +0200	[thread overview]
Message-ID: <5526545F.8040704@freenet.de> (raw)
In-Reply-To: <mailman.2538.1428519743.1448.openembedded-devel@lists.openembedded.org>

On Wed, 8 Apr 2015 11:18:58 Martin Beaudet wrote:
> Hi,
>
> I'm building an image for the beaglebone. I would like to use (at least) the version 5.4 or more of QT with elgfs platform.
> Also the hardware accelerated support on Beaglebone Black.
> ...
> I read about similar error here (https://bugs.launchpad.net/gcc-linaro/+bug/1312931) but they seem to indicate that this error has been fixed in new release of GCC and they are talking about 4.8 so I supposed it has been fixed in 4.9 ?
>
> I hope you can help me out this compiler error because I'm out of idea :(
>
> Best regards,
> Martin
>

Did you try the supposed patch? 
(http://pkgs.fedoraproject.org/cgit/mingw-qt5-qtbase.git/tree/qt5-workaround-gcc48-arm-build-failure.patch?h=f20)

I ran into a similar issue some time ago. Can't remeber which gcc 
version I used or where the error occurred, but for me it solved the ICE 
at var-tracking.c.

Best regards,
Peter


       reply	other threads:[~2015-04-09 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2538.1428519743.1448.openembedded-devel@lists.openembedded.org>
2015-04-09 10:28 ` Peter [this message]
2015-04-08 15:18 Yocto Dizzy + Beaglebone + Qt5 (Internal compiler error) Martin Beaudet

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=5526545F.8040704@freenet.de \
    --to=ppf83764@freenet.de \
    --cc=openembedded-devel@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