I ended up with a reasonable option (commit 28cbc58): in stage 5
(‘%boot5-inputs’), most of the base packages get rebuilt against the new
libc, so they can load the new locale data, but they are rebuilt using
the bootstrap Guile.
In that stage, we also create wrappers for ‘%bootstrap-coreutils&co’
On Mon 31 Aug 2015 13:49, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> On Sun 30 Aug 2015 21:46, l...@gnu.org (Ludovic Courtès) writes:
>>
>>> The binary format for locales is dependent on the libc version. Over
>>> the last few releases, it turned out to be compatible, but
Andy Wingo skribis:
> On Sun 30 Aug 2015 21:46, l...@gnu.org (Ludovic Courtès) writes:
>
>> The binary format for locales is dependent on the libc version. Over
>> the last few releases, it turned out to be compatible, but that of 2.22
>> differs from that of 2.21 (a new element was added to loc
On Sun 30 Aug 2015 21:46, l...@gnu.org (Ludovic Courtès) writes:
> The binary format for locales is dependent on the libc version. Over
> the last few releases, it turned out to be compatible, but that of 2.22
> differs from that of 2.21 (a new element was added to locale categories,
> according
l...@gnu.org (Ludovic Courtès) skribis:
> (The branch is called ‘wip-’ because the glibc upgrade happens to cause
> troubles: since it has new locale category elements, the locale data is
> incompatible with that older libcs expect, which means the bootstrap
> binaries fail with an assertion failu
