From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Andre McCurdy <armccurdy@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] perl-native: Remove usage of -fstack-protector=strong
Date: Fri, 9 Dec 2016 10:23:31 -0600 [thread overview]
Message-ID: <584ADA83.9070709@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYUhvxCxhLAcbwFcnxJSx856DnZBLPjqUHXoW2FAvkQVg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On 12/08/2016 02:35 PM, Burton, Ross wrote:
> On 8 December 2016 at 19:16, Andre McCurdy <armccurdy@gmail.com> wrote:
>
>> 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?
>>
>
> Yes, we recently landed a change so that uninative is versioned by host
> GCC. Presumably that solves this problem in a different way?
If the sstate generated is different from a host distro with gcc>=4.9
and gcc<4.9 will be work.
Could you point me to the patch that makes this change?
alimon
>
> Ross
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-12-09 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 16:34 [PATCH] perl-native: Remove usage of -fstack-protector=strong Aníbal Limón
2016-12-01 22:39 ` Khem Raj
2016-12-01 22:46 ` Aníbal Limón
2016-12-02 0:19 ` Khem Raj
2016-12-08 17:00 ` Aníbal Limón
2016-12-08 19:16 ` Andre McCurdy
2016-12-08 20:35 ` Burton, Ross
2016-12-09 16:23 ` Aníbal Limón [this message]
2016-12-09 20:10 ` Burton, Ross
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=584ADA83.9070709@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.