From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Andrea Adami <andrea.adami@gmail.com>, pb@pbcl.net
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
wesley.lindauer@gmail.com, Kyle Russell <bkylerussell@gmail.com>
Subject: Re: [OE-core] [PATCH] lib: oe: utils: always append host gcc version to NATIVELSBSTRING
Date: Tue, 08 Jun 2021 10:48:36 +0100 [thread overview]
Message-ID: <54d4ce6da8eef4d8e74ad2625d4e6f03b9644a21.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAAQYJAsr=Rh-ie=KKrW=QFg=W2OhbTFNaLOKqeq7sxoH_gRB-Q@mail.gmail.com>
On Tue, 2021-06-08 at 11:20 +0200, Andrea Adami wrote:
> On Tue, Jun 8, 2021 at 12:02 AM Phil Blundell via
> lists.openembedded.org <pb=pbcl.net@lists.openembedded.org> wrote:
> >
> > Wouldn't it be easier to just force -fPIE on for those users for whom this is a problem? Or force -fPIE off for native everywhere. I'm not sure that doing something based on GCC version is obviously the right plan.
> >
> > p.
> >
>
> I was exactly wondering about distro/include/uninative-flags.inc which
> at the time was supposed to fix the changes btw ubuntu 16.x and 18.x.
> But this doesn't seem included nowhere.
Well remembered, I'd fogotten that. It is included by default:
$ grep uninative-flags * -R
meta/conf/distro/defaultsetup.conf:require conf/distro/include/uninative-flags.inc
Cheers,
Richard
next prev parent reply other threads:[~2021-06-08 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 21:25 [PATCH] lib: oe: utils: always append host gcc version to NATIVELSBSTRING bkylerussell
2021-06-07 21:43 ` [OE-core] " Richard Purdie
2021-06-07 22:49 ` bkylerussell
2021-06-08 11:16 ` Richard Purdie
2021-06-08 16:41 ` bkylerussell
2021-06-07 22:01 ` Phil Blundell
2021-06-08 9:20 ` Andrea Adami
2021-06-08 9:48 ` Richard Purdie [this message]
2021-06-08 10:04 ` Andrea Adami
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=54d4ce6da8eef4d8e74ad2625d4e6f03b9644a21.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrea.adami@gmail.com \
--cc=bkylerussell@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
--cc=wesley.lindauer@gmail.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.