Problem with glibc-locale recipe in yocto after the generic C.UTF-8 locale were introduced in glibc
Hi Carlos,
I would like to report that the commit:
https://sourceware.org/git/?p=glibc.git;a=commit;h=466f2be6c08070e9113ae2fdc7acd5d8828cba50
"Add generic C.UTF-8 locale (Bug 17318)"
causes some issues with Yocto/OE build environment, when glibc-locale are build.
PATH="/home/lukma/work/yocto/y2038/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/lukma/work/yocto/y2038/poky/scripts:/home/lukma/work/yocto/y2038/build/tmp/work/armv7vet2hf-neon-poky-linux-gnueabi/glibc-locale/2.34-r0/recipe-sys$ /home/lukma/work/yocto/y2038/build/tmp/work/armv7vet2hf-neon-poky-linux-gnueabi/glibc-locale/2.34-r0/locale-tree//usr/share/i18n/locales/C:60:LC_COLLATE: syntax error/home/lukma/work/yocto/y2038/build/tmp/work/armv7vet2hf-neon-poky-linux-gnueabi/glibc-locale/2.34-r0/locale-tree//usr/share/i18n/locales/C:61:LC_COLLATE: empty category description not allowed [error] too many
errors; giving up
From the patch description I've deduced that this change requires some "ground" work/support for C.UTF-8 locales in the downstream distros.
Apparently poky from newest master (SHA1:1e2e9a84d6dd81d7f6dd69c0d119d0149d10ade1) doesn't provide necessary tools/code.
Carlos, do you have any idea what may be missing to make the OE/Yocto build the glibc-locale again?
Thanks in advance.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: [email protected]