[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-devel
Subject:    [oe] GLIBC_BROKEN_LOCALES
From:       matt.hoosier () gmail ! com (Matt Hoosier)
Date:       2007-10-27 0:35:38
Message-ID: d543f5920710261735i273ddba4v48be826753c8b341 () mail ! gmail ! com
[Download RAW message or body]

On 10/26/07, Richard Purdie <rpurdie at rpsys.net> wrote:
> On Fri, 2007-10-26 at 08:28 -0500, Matt Hoosier wrote:
> > I happened to run afoul of this when trying to build an image for a
> > product that contains tr_TR as one of its localizations.
> >
> > What sort of misbehavior does a locale have to engage in before being
> > banished to this list? I looked at the patches for whichever Ubuntu
> > release also uses glibc-2.5, and can't find any evidence that they do
> > anything to fix the tr_TR localedata in glibc before compiling. Nor do
> > they, as best I can tell, blacklist it the way that OE does.
>
> Usually its failed to build a binary locale under qemu for one or more
> OE devs. I doubt its been investigated more than that. If it does build,
> let us know and we'll probably remove it from the blacklist.

Seems okay for me. I've been building with binary locale generation
enabled. It it matters (since you mentioned qemu), my machine
configuration is targeting xscale.



[prev in list] [next in list] [prev in thread] [next in thread]