Re: stlport5.2: FTBFS on armel: #error Weird WCHAR_MIN or WCHAR_MAX macro value.

2010-11-27 Thread Konstantinos Margaritis
Hi, I got the same error in the armhf port. In more detail, the actual error is caused by the ambiguity in the definition of WCHAR_MAX. On armel/armhf WCHAR_MAX is in fact defined in bits/wchar.h: #define __WCHAR_MAX ( (wchar_t) - 1 ) whereas on amd64 it's defined explicitly as: /* Use GC

Bug#603914: Please drop non-UTF8 locales

2010-11-27 Thread Kalle Olavi Niemitalo
Josselin Mouette writes: > I think wheezy would be a good time to finally ditch non-UTF8 locales. > IIRC, we made the switch to UTF8 by default in etch (and we were already > way too late in doing that), and supporting non-UTF8 stuff becomes > harder and harder, at least for desktop software.