Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/4] gmp.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5
Date: Fri,  5 Feb 2016 11:56:18 -0800	[thread overview]
Message-ID: <1454702179-30239-4-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1454702179-30239-1-git-send-email-armccurdy@gmail.com>

The original over-ride dates back to 2008:

  http://git.openembedded.org/openembedded-core/commit/?id=b3dddcdde5d10f382f71413aad67f7ef2e2420a2

There are no obvious issues seen now when building either of the
current gmp recipes (4.2.1 or 6.1.0) in thumb2 for Cortex A15.

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
 meta/recipes-support/gmp/gmp.inc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-support/gmp/gmp.inc b/meta/recipes-support/gmp/gmp.inc
index 2beea26..abac8cf 100644
--- a/meta/recipes-support/gmp/gmp.inc
+++ b/meta/recipes-support/gmp/gmp.inc
@@ -8,4 +8,5 @@ inherit autotools texinfo
 PACKAGECONFIG ??= ""
 PACKAGECONFIG[readline] = "--with-readline=yes,--with-readline=no,readline"
 
-ARM_INSTRUCTION_SET = "arm"
+ARM_INSTRUCTION_SET_armv4 = "arm"
+ARM_INSTRUCTION_SET_armv5 = "arm"
-- 
1.9.1



  parent reply	other threads:[~2016-02-05 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 19:56 [PATCH 0/4] gmp: misc reformatting + fix gmp_4.2.1 for MIPS Andre McCurdy
2016-02-05 19:56 ` [PATCH 1/4] gmp: move SRC_URI out of gmp.inc + minor reformatting Andre McCurdy
2016-02-05 19:56 ` [PATCH 2/4] gmp: move BBCLASSEXTEND = "native nativesdk" from gmp.inc into 6.1.0 recipe Andre McCurdy
2016-02-05 19:56 ` Andre McCurdy [this message]
2016-02-05 19:56 ` [PATCH 4/4] gmp_4.2.1: fix build for MIPS Andre McCurdy

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=1454702179-30239-4-git-send-email-armccurdy@gmail.com \
    --to=armccurdy@gmail.com \
    --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