From: Pascal Bach <pascal.bach@siemens.com>
To: openembedded-core@lists.openembedded.org
Subject: qemuppc kernel doesn't build with GCC 4.9 on korgoth
Date: Wed, 15 Jun 2016 14:31:23 +0200 [thread overview]
Message-ID: <57614A9B.3090602@siemens.com> (raw)
Hi
I tried to build qemuppc on the latest korgoth branch using the GCC 4.9.3 from OE-core.
The problem is that i get an error when trying to build the kernel.
I was able to trace the issue back to this commit:
https://github.com/openembedded/openembedded-core/commit/7a51776a830167e43cbd185505f62f328704e271
And i can confirm that removing TARGET_CC_KERNEL_ARCH = "-mno-spe" from qemuppc.conf makes it work again.
The question is how to best solve this?
Do the changes for GCC 5.3.0 that done in the commit mentioned above also need to be applied to 4.9?
Or is it just not supported to build qemuppc with GCC 4.9?
Thanks for your help
Pascal
next reply other threads:[~2016-06-15 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 12:31 Pascal Bach [this message]
2016-06-15 19:19 ` qemuppc kernel doesn't build with GCC 4.9 on korgoth Khem Raj
2016-06-16 12:51 ` Pascal Bach
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=57614A9B.3090602@siemens.com \
--to=pascal.bach@siemens.com \
--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