From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] python-native: configure unicode to ucs4
Date: Tue, 14 Sep 2010 14:17:37 -0700 [thread overview]
Message-ID: <4C8FE671.9030205@mentor.com> (raw)
In-Reply-To: <1284493173-27463-1-git-send-email-eric@eukrea.com>
Eric Bénard wrote:
> * while trying to run gdb from an SDK created by OE, I got the following
> errors: /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-gdb: undefined symbol:
> PyUnicodeUCS2_FromEncodedObject
>
> * the reason is that the workstation (ubuntu 10.04 or 9.01)'s Python is compiled using ucs4
> and the python-native used to create arm-angstrom-linux-gnueabi-gdb is using ucs2, the
> problem is detailed here :
> http://docs.python.org/faq/extending#when-importing-module-x-why-do-i-get-undefined-symbol-pyunicodeucs2
>
> * configuring python-native with ucs=4 solves this problem.
>
> Signed-off-by: Eric Bénard <eric@eukrea.com>
Can you test this out on some form of Red Hat? Thanks!
> ---
> recipes/python/python-native_2.6.5.bb | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/recipes/python/python-native_2.6.5.bb b/recipes/python/python-native_2.6.5.bb
> index 66573e9..999335c 100644
> --- a/recipes/python/python-native_2.6.5.bb
> +++ b/recipes/python/python-native_2.6.5.bb
> @@ -20,6 +20,10 @@ S = "${WORKDIR}/Python-${PV}"
>
> inherit native
>
> +EXTRA_OECONF_append = '\
> + --enable-unicode=ucs4 \
> +'
> +
> EXTRA_OEMAKE = '\
> BUILD_SYS="" \
> HOST_SYS="" \
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-14 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 19:39 [PATCH] python-native: configure unicode to ucs4 Eric Bénard
2010-09-14 21:17 ` Tom Rini [this message]
2010-09-17 13:57 ` Eric Bénard
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=4C8FE671.9030205@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.