>>> On 12/01/2016 04:39 PM, Khem Raj wrote: >>>> On Thu, Dec 1, 2016 at 8:34 AM, Aníbal Limón >>>> <anibal.li...@linux.intel.com> wrote: >>>>> Some distributions (like opensuse421) supported by the project >>>>> comes with older gcc releases, -fstack-protector=strong is supported >>>>> by GCC>=4.9. >>>>> >>>>> This causes a build failure when install perl-native from a sstate that >>>>> comes from a machine supporting -fstack-protector=strong [1]. >>>>> >>>>> So disable usage of this flag in perl-native builds, this patch could >>>>> be removed when all supported distros comes with GCC>=4.9. >>>> >>>> Instead of disabling it. Can it be made detectable during configure. >>> >>> The issue here is that comes from SSTATE mirror so the configure step >>> isn't executed again when a other machine without >>> -fstack-protector=strong download the sstate artifact was generate in >>> other machine with -fstack-protector=strong support. This is only for >>> native builds for target builds in enabled. >>> >>> We have similar patches for example in rpm, >>> >>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/rpm/rpm/popt-disable-auto-stack-protector.patch >> >> yeah I see, thanks, I guess we need to bring it down to lowest common >> denominator I guess. >> maybe we should start thinking about gcc-native >>
Is it correct that native sstate from a host with gcc < 4.9 should be reused by a host with gcc >= 4.9 ? Doesn't the change in NATIVELSBSTRING prevent that from happening? -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
