From: Pedro Sanchez <psanchez@fosstel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python standard library problems
Date: Wed, 31 Aug 2011 10:17:23 -0400 [thread overview]
Message-ID: <4E5E4273.7070201@fosstel.com> (raw)
In-Reply-To: <4E5CF562.6070800@fosstel.com>
On 08/30/2011 10:36 AM, Pedro Sanchez wrote:
> Thanks for the patch. I think it's been tested since I see it's
> committed already. But I'll give a try anyway and will let you know.
>
> Thanks!,
>
Buildroot (fresh from git repo) built with the CodeSourcery compiler on
my Ubuntu 10.04 LTS 64-bit worstation.
Tested loading the Python modules of my application. Only one module
fails to load now.
$ python
Python 2.7.1 (r271:86832, Aug 31 2011, 09:38:18)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import fcntl
>>> import os
>>> import sys
>>> import signal
>>> import socket
>>> import time
>>> import datetime
>>> from collections import deque
>>> from subprocess import Popen, PIPE
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.7/subprocess.py", line 432, in <module>
File "/usr/lib/python2.7/pickle.py", line 1266, in <module>
ImportError: No module named binascii
--
Pedro
next prev parent reply other threads:[~2011-08-31 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 19:18 [Buildroot] Python standard library problems Pedro Sanchez
2011-08-10 21:48 ` Dominic Newton
2011-08-11 13:14 ` Pedro Sanchez
2011-08-11 15:37 ` Dominic Newton
2011-08-11 18:23 ` Pedro Sanchez
2011-08-11 20:54 ` Pedro Sanchez
2011-08-12 10:01 ` Maxime Ripard
2011-08-12 15:44 ` Maxime Ripard
2011-08-12 17:47 ` Pedro Sanchez
2011-08-16 8:22 ` Maxime Ripard
2011-08-29 15:58 ` Maxime Ripard
2011-08-30 14:36 ` Pedro Sanchez
2011-08-31 14:17 ` Pedro Sanchez [this message]
2011-09-01 7:50 ` Thomas Petazzoni
2011-09-01 14:18 ` Pedro Sanchez
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=4E5E4273.7070201@fosstel.com \
--to=psanchez@fosstel.com \
--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