Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<p>On Wed, Jun 8, 2011 at 3:40 AM, "Paweł Hajdan, Jr." <<a href="mailto:phajdan.jr@g.o">phajdan.jr@g.o</a>> wrote:<br>
> On 6/7/11 9:53 PM, Matt Turner wrote:<br>
>> Building 400~ locales is not fun on mips when building stages.<br>
><br>
> Do you have some data to quantify "not fun"? How long does it take?</p>
<p>To build glibc</p>
<p>- once for the n32 ABI with only the en_US.UTF-8 locale: 1h 15m<br>
- three times for o32/n32/n64 ABIs with only en_US.UTF-8: 4h 50m<br>
- three times for o32/n32/n64 ABIs with all locales: 6h</p>
<p>I can reconfirm how long it takes just by running locale-gen on all locales, but according to my numbers it takes 1h 10m to generate all the locales.</p>
<p>The o32/n32/n64 configuration is what I've been planning to ship as a compromise between shipping only a single ABI and a set of stages for every ABI, but each ABI adds significant time, and n32 replaces o32 so I'll just plan to drop o32.</p>
<p>So roughly the time required to build all the locales is equal to the time to build glibc for a single ABI.</p>
<p>>> No user has a need for more than some small subset of the total<br>
>> available locales.<br>
>><br>
>> I filed bug [1] to request the ability to select locales in catalyst<br>
>> spec files, but no responses after six months -- which is totally<br>
>> typical of catalyst bugs.<br>
>><br>
>> I commented in bug [2] suggesting that we perhaps reduce the default<br>
>> locale.gen to only 'en_US.UTF-8 UTF-8' or some other limited subset.<br>
><br>
> It makes sense to me, especially for "exotic" arches. It seems that<br>
> locale-gen is cheap anyway on x86 and amd64, where it probably matters most.</p>
<p>Good, thanks for your feedback.</p>
<p>Matt</p>
|
|
