Message 135242 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	dcoles
Recipients	dcoles
Date	2011年05月05日.20:45:29
SpamBayes Score	2.2080387e-06
Marked as misclassified	No
Message-id	<1304628330.77.0.074499731654.issue12010@psf.upfronthosting.co.za>

Content
On Android platforms bionic defines wchar_t as char. This causes compiling of unicodeobject.c to fail with "#error "unsupported wchar_t and PyUNICODE sizes, see issue #8670". The unusual thing is that the configure script does detect if wchar_t is usable (HAVE_USABLE_WCHAR_T) but the wide code support block in unicodeobject.c does not check this (only an #ifdef HAVE_WCHAR_T). Possibly the quick solution is to change this #ifdef to '#if defined(HAVE_WCHAR_T) && defined(HAVE_USABLE_WCHAR_T)'. The header unicodeobject.h does check for HAVE_USABLE_WCHAR_T but will only define HAVE_WCHAR_T if it is not already defined.

Content

On Android platforms bionic defines wchar_t as char. This causes compiling of unicodeobject.c to fail with "#error "unsupported wchar_t and PyUNICODE sizes, see issue #8670".
The unusual thing is that the configure script does detect if wchar_t is usable (HAVE_USABLE_WCHAR_T) but the wide code support block in unicodeobject.c does not check this (only an #ifdef HAVE_WCHAR_T).
Possibly the quick solution is to change this #ifdef to '#if defined(HAVE_WCHAR_T) && defined(HAVE_USABLE_WCHAR_T)'. The header unicodeobject.h does check for HAVE_USABLE_WCHAR_T but will only define HAVE_WCHAR_T if it is not already defined.

History
Date	User	Action	Args
2011年05月05日 20:45:30	dcoles	set	recipients: + dcoles
2011年05月05日 20:45:30	dcoles	set	messageid: <1304628330.77.0.074499731654.issue12010@psf.upfronthosting.co.za>
2011年05月05日 20:45:29	dcoles	link	issue12010 messages
2011年05月05日 20:45:29	dcoles	create

homepage