From: Tobias McNulty <tobias@caktusgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] using linux 2.4 headers AND python
Date: Wed, 25 Mar 2009 20:27:19 -0400 [thread overview]
Message-ID: <49CACBE7.80504@caktusgroup.com> (raw)
In-Reply-To: <20090325232609.GA30311@cloud.net.au>
Hamish Moffatt wrote:
>> Is that line really supposed to be there?
>
> No it isn't, but you should also have the .pyc file (unless you have set
> BR2_PACKAGE_PYTHON_PY_ONLY) so 'import os' will still work. You might
> want to build python with logging and post the log here, ie
>
> make python-dirclean python 2>&1 > pybuild.log
>
> 'svn blame' suggests this is my mistake. I use ..._PYC_ONLY so I didn't
> notice.
Cool, thanks for the quick reply. I do have BR2_PACKAGE_PYTHON_PY_ONLY
selected, but only because that's the default. Is PYC generally
smaller/faster? A quick google seems to suggest that it's not much
faster..but maybe the difference is more noticeable on smaller embedded
machines.
Toby
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
next prev parent reply other threads:[~2009-03-26 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 22:40 [Buildroot] using linux 2.4 headers Tobias McNulty
2009-03-24 22:56 ` Peter Korsgaard
2009-03-25 3:57 ` [Buildroot] using linux 2.4 headers AND python Tobias McNulty
2009-03-25 15:35 ` Tobias McNulty
2009-03-25 23:26 ` Hamish Moffatt
2009-03-26 0:27 ` Tobias McNulty [this message]
2009-03-26 6:57 ` Peter Korsgaard
2009-04-02 0:28 ` Hamish Moffatt
2009-04-02 5:22 ` Peter Korsgaard
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=49CACBE7.80504@caktusgroup.com \
--to=tobias@caktusgroup.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