-
Tor Lillqvist yazdı
I don't understand what the "universal" byte order thing tries to say. Sure, Apple's compilers can produce fat binaries, i.e. containing code for multiple architectures, which I guess might have differing byte order. But I think the test for an -arch flag being present here is backwards, surely if you specify -arch i386 for instance, then we *know* that the byte order is little endian, not "universal". Anyway, this broke ICU when built against MacOSX SDK 10.6 at least, the ICU configury used wrong suffix for ICUDATA_NAME, and genbrk failed in i18npool with a mysterious "can not initialize ICU. status = U_FILE_ACCESS_ERROR" message.
e4050a65
Adı |
Son kayıt (commit)
|
Son güncelleme |
---|---|---|
.. | ||
prj | Loading commit data... | |
Readme | ||
createmak.cfg | ||
createmak.pl | ||
icu-mp.patch | ||
icu4c-4_4_2-wchar_t.patch | ||
icu4c-aix.patch | ||
icu4c-build.patch | ||
icu4c-escapespace.patch | ||
icu4c-rpath.patch | ||
icu4c-strict-c.patch | ||
icu4c-warnings.patch | ||
icu4c.8320.freeserif.crash.patch | ||
icuversion.mk | ||
makefile.mk |