From: Kai Kang <kai.kang@windriver.com>
To: <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 05/19] glibc-locale.inc: add aarch64 to BINARY_LOCALE_ARCHES
Date: Thu, 18 Dec 2014 16:51:01 +0800 [thread overview]
Message-ID: <b49ea4c2927aed8a776a8f2dcf8aab9d5e07eefa.1418885578.git.kai.kang@windriver.com> (raw)
In-Reply-To: <cover.1418885577.git.kai.kang@windriver.com>
Add aarch64 to var BINARY_LOCALE_ARCHES. In libc-packages.class, it is
used to work with other vars to check and add cross-localedef-native as
a dependecy correctly.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
meta/recipes-core/glibc/glibc-locale.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-locale.inc b/meta/recipes-core/glibc/glibc-locale.inc
index d472605..df6d073 100644
--- a/meta/recipes-core/glibc/glibc-locale.inc
+++ b/meta/recipes-core/glibc/glibc-locale.inc
@@ -23,7 +23,7 @@ ENABLE_BINARY_LOCALE_GENERATION_pn-nativesdk-glibc-locale = "0"
#enable locale generation on these arches
# BINARY_LOCALE_ARCHES is a space separated list of regular expressions
-BINARY_LOCALE_ARCHES ?= "arm.* i[3-6]86 x86_64 powerpc mips mips64"
+BINARY_LOCALE_ARCHES ?= "arm.* aarch64 i[3-6]86 x86_64 powerpc mips mips64"
# set "1" to use cross-localedef for locale generation
# set "0" for qemu emulation of native localedef for locale generation
--
1.9.1
next prev parent reply other threads:[~2014-12-18 8:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 8:50 [PATCH 00/19] V3: Add machine qemuarm64 Kai Kang
2014-12-18 8:50 ` [PATCH 01/19] linux-yocto: depend on libgcc for aarch64 Kai Kang
2015-01-01 1:31 ` Khem Raj
2014-12-18 8:50 ` [PATCH 02/19] Add machine qemuarm64 Kai Kang
2014-12-18 8:50 ` [PATCH 03/19] siteinfo: account for 32 and 64 bit arm Kai Kang
2014-12-18 8:51 ` [PATCH 04/19] libc-package.bbclass: add aarch64 target to locale_arch_options Kai Kang
2014-12-18 8:51 ` Kai Kang [this message]
2014-12-18 8:51 ` [PATCH 06/19] libatomics-ops: add aarch64 target iniitial support Kai Kang
2014-12-18 8:51 ` [PATCH 07/19] qt4: add aarch64 support Kai Kang
2014-12-18 8:51 ` [PATCH 08/19] libpng 1.6.13: fix build for aarch64 Kai Kang
2014-12-22 9:41 ` Richard Purdie
2014-12-22 10:57 ` Richard Purdie
2014-12-18 8:51 ` [PATCH 09/19] sysprof: disable " Kai Kang
2014-12-18 8:51 ` [PATCH 10/19] lttng: recognize aarch64 Kai Kang
2014-12-18 8:51 ` [PATCH 11/19] guile: allow compilation for aarch64 Kai Kang
2015-01-01 1:25 ` Khem Raj
2014-12-18 8:51 ` [PATCH 12/19] libunwind: add aarch64 support Kai Kang
2014-12-18 8:51 ` [PATCH 13/19] runqemu: add qemuarm64 support Kai Kang
2015-01-01 1:27 ` Khem Raj
2015-01-04 2:38 ` Kang Kai
2014-12-18 8:51 ` [PATCH 14/19] kexec-tools: add aarch64 support Kai Kang
2014-12-18 8:51 ` [PATCH 15/19] packagegroup-core-tools-profile: remove sysprof for aarch64 Kai Kang
2014-12-18 8:51 ` [PATCH 16/19] gcc: Disable aarch64 multilib options Kai Kang
2014-12-18 8:51 ` [PATCH 17/19] glibc-package: aarch64 enable symlink for ABI compliance Kai Kang
2014-12-18 8:51 ` [PATCH 18/19] aarch-arm64: Update tune files Kai Kang
2015-01-01 1:54 ` Khem Raj
2014-12-18 8:51 ` [PATCH 19/19] linux-yocto: Fixup linux-yocto for aarch64 Kai Kang
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=b49ea4c2927aed8a776a8f2dcf8aab9d5e07eefa.1418885578.git.kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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