From: Chris Smart <mail@csmart.io>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python: apply unicode config to host build
Date: Wed, 22 Feb 2017 14:14:23 +1100 [thread overview]
Message-ID: <20170222031423.GA2574@csmart.io> (raw)
Currently the host build of Python 2 defaults to narrow unicode (UCS2),
ignoring the BR2_PACKAGE_PYTHON_UCS4 configuration option which may be
set to wide (UCS4).
This results in host and target Python packages which are incompatible
in subtle ways.
For example, installing wheels into the target fails when they are made
with the host python, citing incompatibility (as can be seen by the
package tags which may be "cp27u-manylinux1" instead of
"cp27mu-manylinux1").
Compiling the host Python 2 with the same UCS configuration as the
target ensures that the packages are compatible (and the tags match).
This does not affect Python 3 as support for narrow unicode was
deprecated in version 3.3, see https://www.python.org/dev/peps/pep-0393/
Thanks to Tony Breeds <tony@bakeyournoodle.com> for reporting this.
Signed-off-by: Chris Smart <mail@csmart.io>
---
package/python/python.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/python/python.mk b/package/python/python.mk
index 7b20434c94c2b8b8..330716d57f3712f1 100644
--- a/package/python/python.mk
+++ b/package/python/python.mk
@@ -105,6 +105,7 @@ endif
# Default is UCS2 w/o a conf opt
ifeq ($(BR2_PACKAGE_PYTHON_UCS4),y)
+HOST_PYTHON_CONF_OPTS += --enable-unicode=ucs4
PYTHON_CONF_OPTS += --enable-unicode=ucs4
endif
--
2.9.3
next reply other threads:[~2017-02-22 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 3:14 Chris Smart [this message]
2017-02-23 22:13 ` [Buildroot] [PATCH] package/python: apply unicode config to host build Thomas Petazzoni
2017-02-23 23:33 ` Chris Smart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170222031423.GA2574@csmart.io \
--to=mail@csmart.io \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox