>On 02/10/2019 10:07 AM, Xi Ruoyao via lfs-dev wrote:
>> On 2019-02-10 09:54 -0600, Bruce Dubbs via lfs-dev wrote:
>>> On 02/10/2019 06:41 AM, Pierre Labastie via lfs-dev wrote:
On 10/02/2019 08:45, Brandon Murry via lfs-dev wrote:
> Hi, I hope this is the right place to put this.
>
Rebuilt everything from scratch again. Still same issue with the chapter 6
glibc build. There must be something with the host system files getting
linked or something.
Running openSUSE Tumbleweed (latest) with all host system requirements met.
I've meticulously gone through trying to make sure
On 2/12/19 10:10 AM, Pierre Labastie via lfs-dev wrote:
First:
localedef -i POSIX -f UTF-8 C.UTF-8
generates warnings and has exit code 1! So it is not
suitable for scripting (at least with "set -e").
Looking at what debian does, they have a patch to generate
a file named "C" in
On 12/02/2019 17:10, Pierre Labastie via lfs-dev wrote:
First:
localedef -i POSIX -f UTF-8 C.UTF-8
generates warnings and has exit code 1! So it is not
suitable for scripting (at least with "set -e").
Looking at what debian does, they have a patch to generate
a file named "C" in
First:
localedef -i POSIX -f UTF-8 C.UTF-8
generates warnings and has exit code 1! So it is not
suitable for scripting (at least with "set -e").
Looking at what debian does, they have a patch to generate
a file named "C" in localedata/locales. While the "POSIX" file
shipped with glibc contains
On 11/02/2019 22:49, Bruce Dubbs via lfs-dev wrote:
> On 02/11/2019 03:19 PM, Pierre Labastie via lfs-dev wrote:
>> On 11/02/2019 19:49, Bruce Dubbs via lfs-dev wrote:
>>> On 02/11/2019 12:10 PM, Douglas R. Reno via lfs-dev wrote:
>>>
While we're here, can we please add the C.UTF-8 locale?
On 12/02/2019 05:10, Brandon Murry via lfs-dev wrote:
> I've been attacking this new Glibc 2.29 for over a week and keep running in to
> this error. During the installation of locales, the localedef program is run,
> except it fails everytime saying that it cannot load "libc.so.6".
> Ldd on the
