From: Winfried <winfried_mb2@xmsnet.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-java] gcc6 support breaks build for gcc < 6
Date: Tue, 12 Jul 2016 13:56:59 +0200 [thread overview]
Message-ID: <a53144a4c8faa1ec968e6aefdad47e01@xmsnet.nl> (raw)
In-Reply-To: <14c344e66a5112f492cc21c9a7d0f217@xmsnet.nl>
>>> | ERROR: Function failed: do_configure (log file is located at
>>> /home/jacopo/yjp/poky/build/tmp/work/x86_64-linux/openjdk-8-native/72b05-r0/temp/log.do_configure.2980
>>>
>>> I'm running on ubuntu 14.04 with gcc4.8 and openjdk 1.8, i don't
>>> think it's a side effect of the gcc6 patch, but in your opinion, i
>>> forgot something?
>>>
>>
>> this is building openjdk-8-native package. So you need to add a
>> bbappend for openjdk-8-native_72b05.bb as well
>
> already done:
>
> ➜ openjdk git:(develop) cat openjdk-8-native_72b05.bbappend
> CFLAGS_remove = "-fno-lifetime-dse"
> CXXFLAGS_remove = "-fno-lifetime-dse"
>
> openjdk-8 is not a recipe, correct? any suggestion?
>
> thank you. jacob
Here is the .bbappend that works for me:
wdobbe@tc-linux-build2:~/yocto/peek-krogoth/sources/meta-peek/recipes-core/openjdk>
cat openjdk-8-native_%.bbappend
CFLAGS_remove = "-fno-lifetime-dse"
CXXFLAGS_remove = "-fno-lifetime-dse"
next prev parent reply other threads:[~2016-07-12 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 15:19 [meta-java] gcc6 support breaks build for gcc < 6 Winfried
2016-07-11 22:32 ` [meta-java] gcc 4.8 and openjdk-8 Jacopo Malvestio
2016-07-11 23:48 ` Khem Raj
2016-07-12 5:09 ` Jacopo Malvestio
2016-07-12 23:23 ` Khem Raj
2016-07-15 9:47 ` Jacopo Malvestio
2016-07-15 18:03 ` Dan McGregor
2016-07-12 11:56 ` Winfried [this message]
2016-07-12 16:48 ` [meta-java] gcc6 support breaks build for gcc < 6 Jacopo Malvestio
-- strict thread matches above, loose matches on Subject: below --
2016-07-11 11:37 Winfried
2016-07-11 13:19 ` Otavio Salvador
2016-07-11 14:24 ` Khem Raj
2016-07-11 14:28 ` Otavio Salvador
2016-07-11 14:37 ` Khem Raj
2016-07-12 4:52 ` Dan McGregor
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=a53144a4c8faa1ec968e6aefdad47e01@xmsnet.nl \
--to=winfried_mb2@xmsnet.nl \
--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