From: Xiangyu Chen <[email protected]>

Some locales are not listed in glibc locales support list, but can be generated,
here using ja_JP.SHIFT_JIS as an example. We can add following line into 
local.conf
to enable and generate it:

GLIBC_GENERATE_LOCALES += "en_GB.UTF-8 en_US.UTF-8 ja_JP.UTF-8 ja_JP.SHIFT_JIS"
IMAGE_LINGUAS += "ja-jp en-us ja-jp.shift-jis"

The localedef tool would report a warning and exit with 1, that cause build 
failure,
error message as below:

[warning] character map `SHIFT_JIS' is not ASCII compatible, locale not ISO C 
compliant [--no-warnings=ascii]

So add a --no-warnings=ascii in libc-package.bbclass to fix build failure if 
someone needs those locale
in yocto.

Signed-off-by: Xiangyu Chen <[email protected]>
---
 meta/classes-recipe/libc-package.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/libc-package.bbclass 
b/meta/classes-recipe/libc-package.bbclass
index bf160b115d..c06a2ce90a 100644
--- a/meta/classes-recipe/libc-package.bbclass
+++ b/meta/classes-recipe/libc-package.bbclass
@@ -278,7 +278,7 @@ python package_do_split_gconvs () {
                 bb.fatal("unknown arch:" + target_arch + " for 
locale_arch_options")
 
             localedef_opts += " --force --no-hard-links --no-archive 
--prefix=%s \
-                --inputfile=%s/%s/i18n/locales/%s --charmap=%s %s/%s" \
+                --inputfile=%s/%s/i18n/locales/%s --charmap=%s %s/%s 
--no-warnings=ascii" \
                 % (treedir, treedir, datadir, locale, encoding, outputpath, 
name)
 
             cmd = "PATH=\"%s\" I18NPATH=\"%s\" GCONV_PATH=\"%s\" 
cross-localedef %s" % \
-- 
2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196197): 
https://lists.openembedded.org/g/openembedded-core/message/196197
Mute This Topic: https://lists.openembedded.org/mt/104579284/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to