Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] security_flags.inc: add more exceptions
Date: Wed, 15 Apr 2015 12:10:26 +0300	[thread overview]
Message-ID: <552E2B02.8020105@mentor.com> (raw)
In-Reply-To: <4A2072A0-6C21-4FE5-98D6-C9EEB1FA3924@gmail.com>

On 04/10/2015 03:28 AM, Khem Raj wrote:
>
>> On Apr 9, 2015, at 12:58 PM, Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com> wrote:
>>
>> Add few more exceptions from other layers as noted during custom image
>> builds.
>>
>
> you can put it in respective layer.conf its seems a bit auxiliary to have it in OE-Core

Would it be better to fix the layer.conf or individual recipes?

>
>> Signed-off-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
>> ---
>> meta/conf/distro/include/security_flags.inc | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc
>> index 21e1a53..f977c8e 100644
>> --- a/meta/conf/distro/include/security_flags.inc
>> +++ b/meta/conf/distro/include/security_flags.inc
>> @@ -58,8 +58,10 @@ SECURITY_CFLAGS_pn-libglu = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libpcap = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libpcre = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-libproxy = "${SECURITY_NO_PIE_CFLAGS}"
>> +SECURITY_CFLAGS_pn-libvirt = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-ltp = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-lttng-ust = "${SECURITY_NO_PIE_CFLAGS}"
>> +SECURITY_CFLAGS_pn-lvm2 = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-mesa = "${SECURITY_NO_PIE_CFLAGS}"
>> SECURITY_CFLAGS_pn-mesa-gl = "${SECURITY_NO_PIE_CFLAGS}"

[ skipped the rest]


-- 
With best wishes
Dmitry


  reply	other threads:[~2015-04-15  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 19:58 [PATCH 1/4] groff: add runtime dependency on sed Dmitry Eremin-Solenikov
2015-04-09 19:58 ` [PATCH 2/4] bitbake.conf: add sed-native to ASSUME_PROVIDED Dmitry Eremin-Solenikov
2015-04-09 19:58 ` [PATCH 3/4] security_flags.inc: add more exceptions Dmitry Eremin-Solenikov
2015-04-10  0:28   ` Khem Raj
2015-04-15  9:10     ` Dmitry Eremin-Solenikov [this message]
2015-04-16 21:07       ` Khem Raj
2015-04-09 19:58 ` [PATCH 4/4] lsb: provide lsb-core-ARCH Dmitry Eremin-Solenikov
2015-04-11 22:27   ` Richard Purdie

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=552E2B02.8020105@mentor.com \
    --to=dmitry_eremin@mentor.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox