From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] using linux 2.4 headers AND python
Date: Thu, 26 Mar 2009 10:26:10 +1100 [thread overview]
Message-ID: <20090325232609.GA30311@cloud.net.au> (raw)
In-Reply-To: <49CA4F52.705@caktusgroup.com>
On Wed, Mar 25, 2009 at 11:35:46AM -0400, Tobias McNulty wrote:
> Tobias McNulty wrote:
> > and, sure enough, I don't see os.py anywhere on the filesystem. I have
> > not looked at the python build output yet but I'll do that tomorrow when
> > I'm more awake.
>
> Sure enough, the installer is installing all the .py files and then
> removing them again. It appears the line at fault is the last one in
> the following section of python.mk
>
> ifneq ($(BR2_PACKAGE_PYTHON_DEV),y)
> rm -rf $(TARGET_DIR)/usr/include/python$(PYTHON_VERSION_MAJOR)
> rm -rf
> $(TARGET_DIR)/usr/lib/python$(PYTHON_VERSION_MAJOR)/config
> find $(TARGET_DIR)/usr/lib/ -name '*.py' -exec rm {} \;
> endif
>
> 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.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2009-03-25 23:26 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 [this message]
2009-03-26 0:27 ` Tobias McNulty
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=20090325232609.GA30311@cloud.net.au \
--to=hamish@cloud.net.au \
--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