Re: Should we make 'icu4c' identical between platforms?

2019-07-31 Thread Marius Bakke
Mark H Weaver writes: > Hi Marius, > > Marius Bakke wrote: >> For now, I'm leaning towards adding the above substitution >> unconditionally, and remove the "--with-data-packaging=archive" flag, so >> that ICU has the same bugs (and builds!) everywhere. >> >> Mark, WDYT? > > Sure, sounds good to

Re: Should we make 'icu4c' identical between platforms?

2019-07-25 Thread Mark H Weaver
Hi Marius, Marius Bakke wrote: > For now, I'm leaning towards adding the above substitution > unconditionally, and remove the "--with-data-packaging=archive" flag, so > that ICU has the same bugs (and builds!) everywhere. > > Mark, WDYT? Sure, sounds good to me. Thanks! Mark

Re: Should we make 'icu4c' identical between platforms?

2019-07-24 Thread Marius Bakke
Marius Bakke writes: > Hello listers and lurkers, > > On MIPS and 32-bit ARM platforms, 'icu4c' is built with > '--with-data-packaging=archive'. The effect is that the locale data is > stored in a single "icudt__.dat" instead of in the shared library: > > http://userguide.icu-project.org/icudata

Should we make 'icu4c' identical between platforms?

2019-07-24 Thread Marius Bakke
Hello listers and lurkers, On MIPS and 32-bit ARM platforms, 'icu4c' is built with '--with-data-packaging=archive'. The effect is that the locale data is stored in a single "icudt__.dat" instead of in the shared library: http://userguide.icu-project.org/icudata There are no comments mentioning