From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 3/7] klibc.inc: use x86 over-ride instead of i486/i586/i686
Date: Thu, 4 Jun 2015 12:21:02 -0700 [thread overview]
Message-ID: <1433445666-7207-3-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1433445666-7207-1-git-send-email-armccurdy@gmail.com>
32bit x86 is covered by the x86 over-ride, so duplicate over-rides for
i486/i586/i686 are not required.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
meta-initramfs/recipes-devtools/klibc/klibc.inc | 3 ---
1 file changed, 3 deletions(-)
diff --git a/meta-initramfs/recipes-devtools/klibc/klibc.inc b/meta-initramfs/recipes-devtools/klibc/klibc.inc
index 9f445e1..41b0b29 100644
--- a/meta-initramfs/recipes-devtools/klibc/klibc.inc
+++ b/meta-initramfs/recipes-devtools/klibc/klibc.inc
@@ -44,9 +44,6 @@ KLIBC_ARCH_armeb = "arm"
KLIBC_ARCH_mipsel = "mips"
KLIBC_ARCH_x86 = "i386"
KLIBC_ARCH_x86-64 = "x86_64"
-KLIBC_ARCH_i486 = "i386"
-KLIBC_ARCH_i586 = "i386"
-KLIBC_ARCH_i686 = "i386"
KLIBC_ARCH_pentium = "i386"
KLIBC_ARCH_powerpc = "ppc"
KLIBC_ARCH_powerpc64 = "ppc64"
--
1.9.1
next prev parent 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 [meta-oe][PATCH 1/7] elbow: use x86 over-ride instead of i586 Andre McCurdy
2015-06-04 19:21 ` [meta-oe][PATCH 2/7] webkit-efl.inc: " Andre McCurdy
2015-06-04 19:21 ` Andre McCurdy [this message]
2015-06-04 19:34 ` [meta-oe][PATCH 3/7] klibc.inc: use x86 over-ride instead of i486/i586/i686 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-3-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox