From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-initramfs][PATCH 4/5] klibc.bbclass: Pass TUNE_CCARGS in flags
Date: Mon, 2 Oct 2017 09:06:56 -0700 [thread overview]
Message-ID: <20171002160657.39576-4-raj.khem@gmail.com> (raw)
In-Reply-To: <20171002160657.39576-1-raj.khem@gmail.com>
This is needed for ABI compatibility since
march defines if -mthumb means thumb1 or thumb2
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta-initramfs/classes/klibc.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-initramfs/classes/klibc.bbclass b/meta-initramfs/classes/klibc.bbclass
index 1ec7b2b05..b7b72b728 100644
--- a/meta-initramfs/classes/klibc.bbclass
+++ b/meta-initramfs/classes/klibc.bbclass
@@ -11,6 +11,6 @@ CC_append_armv7a = " ${@' -mfloat-abi=${TUNE_CCARGS_MFLOAT}' if (d.getVar('TUNE_
CPP_forcevariable = "${CC} -E"
# klcc uses own optimizations by default. See klcc(1) man file.
-export CFLAGS=""
-export CPPFLAGS=""
-export LDFLAGS=""
+export CFLAGS="${TUNE_CCARGS}"
+export CPPFLAGS="${TUNE_CCARGS}"
+export LDFLAGS="${TUNE_CCARGS}"
--
2.14.2
next prev parent reply other threads:[~2017-10-02 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 16:06 [meta-initramfs][PATCH 1/5] klibc: Pass Optimization with KLIBCOPTFLAGS Khem Raj
2017-10-02 16:06 ` [meta-python][PATCH 2/5] python-m2crypto: Upgrade to 0.26.4 Khem Raj
2017-10-02 16:06 ` [meta-initramfs][PATCH 3/5] ubi-utils-klibc: Update to 1.5.2 release of mtd-utils Khem Raj
2017-10-02 21:10 ` Andrea Adami
2017-10-02 16:06 ` Khem Raj [this message]
2017-10-02 16:06 ` [meta-oe][PATCH 5/5] gperftools: Enable on mips Khem Raj
2018-04-10 2:19 ` ChenQi
2017-10-03 19:28 ` [meta-initramfs][PATCH 1/5] klibc: Pass Optimization with KLIBCOPTFLAGS Khem Raj
2017-10-03 19:33 ` Martin Jansa
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=20171002160657.39576-4-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