From: Dominic Newton <dominic.newton@in-2-technology.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Python standard library problems
Date: Thu, 11 Aug 2011 16:37:16 +0100 [thread overview]
Message-ID: <4E43F72C.4060005@in-2-technology.co.uk> (raw)
In-Reply-To: <4E43D5B4.2090106@fosstel.com>
Hi
Yes I'm using the native toolchain. One thing to check might be any
dependencies the modules you are trying to build - for example have you
got appropriate libraries being built before python for networking which
will get _socket built.
The easiest way to look at the setup.py output is to redirect the stdout
to a file and then inspect it, any messages regarding module builds will
be there. If python cannot build a module it won't stop, but just sends
some output to the console. It is possible to edit setup.py to output
results direct to a log file, but this can take a while to sort out.
Not sure if this is much help as this has (so far) always worked for me
out of the box for a number of targets.
Dominic Newton
In 2 Technology Ltd.
next prev parent reply other threads:[~2011-08-11 15:37 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 [this message]
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
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=4E43F72C.4060005@in-2-technology.co.uk \
--to=dominic.newton@in-2-technology.co.uk \
--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