From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 1/7] elbow: use x86 over-ride instead of i586
Date: Thu, 4 Jun 2015 12:21:00 -0700 [thread overview]
Message-ID: <1433445666-7207-1-git-send-email-armccurdy@gmail.com> (raw)
Support i686 without needing to duplicate the i586 over-ride.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
meta-efl/recipes-efl/e17/elbow_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-efl/recipes-efl/e17/elbow_git.bb b/meta-efl/recipes-efl/e17/elbow_git.bb
index 16664f9..064b794 100644
--- a/meta-efl/recipes-efl/e17/elbow_git.bb
+++ b/meta-efl/recipes-efl/e17/elbow_git.bb
@@ -8,7 +8,7 @@ SRCREV = "b41fd0bc9514ff61bb2a50d957efe4155fa3e6a8"
# webkit-efl isn't available for < armv7a
COMPATIBLE_MACHINE = "(-)"
-COMPATIBLE_MACHINE_i586 = "(.*)"
+COMPATIBLE_MACHINE_x86 = "(.*)"
COMPATIBLE_MACHINE_x86-64 = "(.*)"
COMPATIBLE_MACHINE_armv7a = "(.*)"
--
1.9.1
next reply other threads:[~2015-06-04 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 19:21 Andre McCurdy [this message]
2015-06-04 19:21 ` [meta-oe][PATCH 2/7] webkit-efl.inc: use x86 over-ride instead of i586 Andre McCurdy
2015-06-04 19:21 ` [meta-oe][PATCH 3/7] klibc.inc: use x86 over-ride instead of i486/i586/i686 Andre McCurdy
2015-06-04 19:34 ` Khem Raj
2015-06-04 20:57 ` [meta-oe][PATCH v2 3/7] klibc.inc: use x86 over-ride instead of i486/i586/i686/pentium Andre McCurdy
2015-06-04 19:21 ` [meta-oe][PATCH 4/7] gst-plugins-base: use x86 over-ride instead of i586 Andre McCurdy
2015-06-04 19:21 ` [meta-oe][PATCH 5/7] luajit: " Andre McCurdy
2015-06-04 19:21 ` [meta-oe][PATCH 6/7] emacs.inc: " Andre McCurdy
2015-06-04 19:21 ` [meta-oe][PATCH 7/7] mariadb.inc: " 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=1433445666-7207-1-git-send-email-armccurdy@gmail.com \
--to=armccurdy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.