All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Khem Raj <raj.khem@gmail.com>
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 14:03:39 -0300	[thread overview]
Message-ID: <CAP9ODKrhZPZNHfYMc0H=VNdjqY=_rGOfWpEXF6FnU58XRdnotA@mail.gmail.com> (raw)
In-Reply-To: <EEE571F8-C3A1-49F6-89B6-30D5F50B972D@gmail.com>

On Tue, Oct 13, 2015 at 2:02 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
>> On Oct 13, 2015, at 9:59 AM, Otavio Salvador <otavio.salvador@ossystems.com.br> wrote:
>>
>> On Tue, Oct 13, 2015 at 1:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>>> 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.
>>
>> Right but in this case:
>>
>> - we fix it to not rebuild it
>> - we fix why it is not building it
>>
>> I am a complete ignorant in glibc build system. Can you help on this one?
>
> share the complete logs for first time and second time builds somewhere.

I will try to come up with  a way to reproduce it. I don't have the
logs anymore.

-- 
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


  reply	other threads:[~2015-10-13 17:03 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
2015-10-13 16:59       ` Otavio Salvador
2015-10-13 17:02         ` Khem Raj
2015-10-13 17:03           ` Otavio Salvador [this message]
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='CAP9ODKrhZPZNHfYMc0H=VNdjqY=_rGOfWpEXF6FnU58XRdnotA@mail.gmail.com' \
    --to=otavio.salvador@ossystems.com.br \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.