Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: glibc build error when it is rebuild due hash mismatch
Date: Tue, 13 Oct 2015 09:54:29 -0700	[thread overview]
Message-ID: <CE766E63-DA13-44FF-AE6A-B76615CE56DA@gmail.com> (raw)
In-Reply-To: <CAP9ODKoN8S-nqASuUsRzt_qeuPGBuhsoHPeH_NFHEGbHWbGd+Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]


> On Oct 13, 2015, at 9:53 AM, Otavio Salvador <otavio.salvador@ossystems.com.br> wrote:
> 
> On Tue, Oct 13, 2015 at 1:52 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> 
>>> On Oct 13, 2015, at 9:45 AM, Otavio Salvador <otavio.salvador@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.
> 
> First build works fine; rebuild fails. So I am not sure this is the culprit.

it might not be rebuilding message catalog first time.

> 
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2015-10-13 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 16:45 glibc build error when it is rebuild due hash mismatch Otavio Salvador
2015-10-13 16:52 ` Khem Raj
2015-10-13 16:53   ` Otavio Salvador
2015-10-13 16:54     ` Khem Raj [this message]
2015-10-13 16:59       ` Otavio Salvador
2015-10-13 17:02         ` Khem Raj
2015-10-13 17:03           ` Otavio Salvador
2015-10-14  5:03   ` Richard Purdie
2015-10-14  5:10     ` Khem Raj
2015-10-14 12:51       ` Otavio Salvador

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=CE766E63-DA13-44FF-AE6A-B76615CE56DA@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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