Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 3/4] crash: Pass optimization flags to configure via CC
Date: Tue, 27 Jun 2017 23:14:17 -0700	[thread overview]
Message-ID: <20170628061418.16693-3-raj.khem@gmail.com> (raw)
In-Reply-To: <20170628061418.16693-1-raj.khem@gmail.com>

This is because when using fortify warnings we need to have
some level of optimization, while we append warnings to CC
we dont do the same for optimization, which results in compile
failures when doing build with hardened flags

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 meta-oe/recipes-kernel/crash/crash_7.1.9.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-oe/recipes-kernel/crash/crash_7.1.9.bb b/meta-oe/recipes-kernel/crash/crash_7.1.9.bb
index 93208e398..d40937e93 100644
--- a/meta-oe/recipes-kernel/crash/crash_7.1.9.bb
+++ b/meta-oe/recipes-kernel/crash/crash_7.1.9.bb
@@ -35,6 +35,7 @@ SRC_URI[gdb.sha256sum] = "8070389a5dcc104eb0be483d582729f98ed4d761ad19cedd3f17b5
 inherit gettext
 
 BBCLASSEXTEND = "native cross"
+TARGET_CC_ARCH_append = " ${SELECTED_OPTIMIZATION}"
 
 # crash 7.1.3 and before don't support mips64
 COMPATIBLE_HOST = "^(?!mips64).*"
-- 
2.13.2



  parent reply	other threads:[~2017-06-28  6:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28  6:14 [meta-oe][PATCH 1/4] cdrkit: Fix build with hardening flags Khem Raj
2017-06-28  6:14 ` [meta-oe][PATCH 2/4] orrery: " Khem Raj
2017-06-28  6:14 ` Khem Raj [this message]
2017-06-28  6:14 ` [meta-oe][PATCH V2 4/4] ipmiutil: Update to 3.0.5 Khem Raj

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=20170628061418.16693-3-raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --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