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: Wed, 14 Oct 2015 09:51:03 -0300 [thread overview]
Message-ID: <CAP9ODKpeMm9Opf3r8W7h=VN60BKs-jieEANN0D=+ydvU=mLPmQ@mail.gmail.com> (raw)
In-Reply-To: <B678E6C6-E7F6-4256-84D9-C53DE739D630@gmail.com>
On Wed, Oct 14, 2015 at 2:10 AM, Khem Raj <raj.khem@gmail.com> wrote:
>> On Oct 13, 2015, at 10:03 PM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
>> 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.
I prefer option 2, with a packageconfig and possibility to enable its
generation in a distro, if needed.
--
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
prev parent reply other threads:[~2015-10-14 12:51 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
2015-10-14 5:03 ` Richard Purdie
2015-10-14 5:10 ` Khem Raj
2015-10-14 12:51 ` Otavio Salvador [this message]
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='CAP9ODKpeMm9Opf3r8W7h=VN60BKs-jieEANN0D=+ydvU=mLPmQ@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.