[OE-core] glibc build error when it is rebuild due hash mismatch

Khem Raj raj.khem at gmail.com
Wed Oct 14 05:10:34 UTC 2015


> On Oct 13, 2015, at 10:03 PM, Richard Purdie <richard.purdie at linuxfoundation.org> wrote:
> 
> On Tue, 2015-10-13 at 09:52 -0700, Khem Raj wrote:
>>> On Oct 13, 2015, at 9:45 AM, Otavio Salvador <otavio.salvador at ossystems.com.br> wrote:
>>> 
>>> Hello,
>>> 
>>> From time to time I see following error:
>>> 
>>> | /usr/bin/install -c -m 644
>>> /home/otavio/src/yocto/build/tmp/work/cortexa9hf-vfp-neon-oel-linux-gnueabi/glibc/2.22-r0/build-arm-oel-linux-gnueabi/gnu/option-groups.h
>>> /home/otavio/src/yocto/build/tmp/work/cortexa9hf-vfp-neon-oel-linux-gnueabi/glibc/2.22-r0/image/usr/include/gnu/option-groups.h
>>> | /usr/bin/install -c -m 644
>>> /home/otavio/src/yocto/build/tmp/work/cortexa9hf-vfp-neon-oel-linux-gnueabi/glibc/2.22-r0/build-arm-oel-linux-gnueabi/gnu/lib-names-hard.h
>>> /home/otavio/src/yocto/build/tmp/work/cortexa9hf-vfp-neon-oel-linux-gnueabi/glibc/2.22-r0/image/usr/include/gnu/lib-names-hard.h
>>> | msgfmt -o rw.mo rw.po
>>> | /bin/bash: msgfmt: command not found
>>> | Makefile:84: recipe for target 'rw.mo' failed
>>> | make[2]: *** [rw.mo] Error 127
>>> | make[2]: *** Waiting for unfinished jobs....
>>> | make[2]: Leaving directory
>>> '/home/otavio/src/yocto/build/tmp/work/cortexa9hf-vfp-neon-oel-linux-gnueabi/glibc/2.22-r0/git/po'
>>> | Makefile:234: recipe for target 'po/subdir_install' failed
>>> 
>>> and it seems to happen when a rebuild of glibc is triggered due a
>>> change in the sstate hash. The host is a very minimal system so it
>>> explains why it does not provide the msgfmt in host and also might
>>> explain why it is not being catch in Yocto Project AB.
>> 
>> 
>> are we missing a dependency on gettext-native ? it could be that AB slaves have gettext installed on host
>> and you don’t.
> 
> Agreed, this does look like a missing gettext-native dependency
> somewhere in the system. Unfortunately gettext(native) is a pretty heavy
> dependency too :(

We have two options
1. Ask for it on host ( can cause discrepancies)
2. Workout glibc to not rebuild message catalogs at any cost.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20151013/d94f0adf/attachment-0002.sig>


More information about the Openembedded-core mailing list