From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/2] uclibc: no need for CONFIG_MIPS_ISA_xxx config options
Date: Fri, 10 Jun 2016 16:12:12 +0100 [thread overview]
Message-ID: <1465571533-21604-1-git-send-email-git@andred.net> (raw)
From: André Draszik <adraszik@tycoint.com>
The config option for the mips ISA have been completely removed
from uclibc-ng. uclibc doesn't add gcc options based on those
config options anymore. Hence we don't need to create them here
either.
Signed-off-by: André Draszik <adraszik@tycoint.com>
---
meta/recipes-core/uclibc/uclibc.inc | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/meta/recipes-core/uclibc/uclibc.inc b/meta/recipes-core/uclibc/uclibc.inc
index 1d42284..71d4bdd 100644
--- a/meta/recipes-core/uclibc/uclibc.inc
+++ b/meta/recipes-core/uclibc/uclibc.inc
@@ -88,16 +88,6 @@ python () {
if "${OE_DEL}":
d.setVar('configmangle_append', "${OE_DEL}" + "\n")
- # by default uclibc uses mips1 ISA for o32 ABI
- # if we use TARGET_CC_ARCH="-march=mips32" we end up
- # with conflicting march options to gcc. Here we
- # ask for MIPS32 ISA to match the chosen arch
- tune = d.getVar("DEFAULTTUNE", True)
- if tune.startswith('mips32'):
- import re
- tune = re.sub('(el)*(-nf)*', '', tune)
- d.setVar('configmangle_append',
- "/^### MIPS32_CHECK$/a\\\nCONFIG_MIPS_ISA_%s=y\n\n" % (tune.upper()))
if "${OE_FEATURES}":
d.setVar('configmangle_append',
"/^### DISTRO FEATURES$/a\\\n%s\n\n" %
@@ -146,7 +136,6 @@ do_configure() {
echo "### FPU" >>${S}/merged.config
echo "### ABI" >>${S}/merged.config
echo "### DISTRO FEATURES" >>${S}/merged.config
- echo "### MIPS32_CHECK" >>${S}/merged.config
# Mangle the resulting .config depending on OE variables
sed -i -e '${configmangle}' ${S}/merged.config
--
2.8.1
next reply other threads:[~2016-06-10 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 15:12 André Draszik [this message]
2016-06-10 15:12 ` [PATCH 2/2] uclibc: never build with SSP André Draszik
2016-06-16 0:20 ` Khem Raj
2016-06-20 14:48 ` André Draszik
2016-06-20 15:21 ` André Draszik
2016-06-21 16:12 ` 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=1465571533-21604-1-git-send-email-git@andred.net \
--to=git@andred.net \
--cc=openembedded-core@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