From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Problem with buildtools-tarball / nativesdk-ncurses / nativesdk-python
Date: Wed, 19 Jun 2013 08:56:50 +0100 [thread overview]
Message-ID: <1371628610.20823.155.camel@ted> (raw)
In-Reply-To: <51C11201.2010306@windriver.com>
On Tue, 2013-06-18 at 21:05 -0500, Mark Hatle wrote:
> My host system's python version is too old due to the recent changes. So I
> built a temporary python 2.7.3 version. Built the 'buildtools-tarball' and then
> installed it. When I switch to the included python it no longer works.
>
> I did some digging, the problem in the end is related to ncurses within the
> nativesdk.
>
> Running the following:
> py_v26_check=`python -c 'import sys; print sys.version_info >= (2,6,3)'`
> which python
> echo "$py_v26_check" | od -c
> if [ "$py_v26_check" != "True" ]; then
> echo "BitBake requires Python 2.7.3 or later"
> exit 1
> fi
>
> You can see the difference in behavior:
>
> TERM=xterm
>
> /home/lmhatle/build-qemux86_64-2/buildtools/sysroots/x86_64-wrlinuxsdk-linux/usr/bin/python
> 0000000 033 [ ? 1 0 3 4 h T r u e \n
> 0000015
> BitBake requires Python 2.7.3 or later
>
> -----
>
> TERM=vt100
>
> /home/lmhatle/build-qemux86_64-2/buildtools/sysroots/x86_64-wrlinuxsdk-linux/usr/bin/python
> 0000000 T r u e \n
> 0000005
>
> -----
>
> So as you can see specifying a different terminal type is happily changing the
> output of python. When I use my locally built version, I don't get the same
> behavior. I always get the second version.
>
> So is there a problem with the nativesdk python, nativesdk ncurses or???
>
> (I've not yet filed a bug on this, but I will if I can't figure it out soon.)
We've seen this issue but I thought we'd fixed it.
Which version of master did you do this with? This was supposed to be
fixed by
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c281cd149bdbce29fc69cb34c65c4295cfed2060 and http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=534c4d0f1e287d0ac82504b273a5497d3457582a
If you're still having problems, please strace the above python command
and see where its looking for terminfo...
Cheers,
Richard
next prev parent reply other threads:[~2013-06-19 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 2:05 Problem with buildtools-tarball / nativesdk-ncurses / nativesdk-python Mark Hatle
2013-06-19 7:56 ` Richard Purdie [this message]
2013-06-19 15:27 ` Mark Hatle
2013-06-19 16:47 ` Mark Hatle
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=1371628610.20823.155.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@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.