From: Tobias McNulty <tobias@caktusgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] using linux 2.4 headers AND python
Date: Wed, 25 Mar 2009 11:35:46 -0400 [thread overview]
Message-ID: <49CA4F52.705@caktusgroup.com> (raw)
In-Reply-To: <49C9ABB0.8080501@caktusgroup.com>
Tobias McNulty wrote:
> Upon further investigation Python doesn't seem to be complete though:
>
> $ python -v
> Could not find platform independent libraries <prefix>
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> # installing zipimport hook
> import zipimport # builtin
> # installed zipimport hook
> 'import site' failed; traceback:
> ImportError: No module named site
> Python 2.4.5 (#1, Mar 24 2009, 23:15:27)
> [GCC 4.3.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import os
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> ImportError: No module named os
>
> 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?
BR2_PACKAGE_PYTHON_DEV says:
"If enabled, development files (headers and static libpython) will be
installed on the target. "
It seems to me, if you have this disabled, you still might want the
basic python library installed on the target (especially if you set
BR2_PACKAGE_PYTHON_PY_ONLY=y)!
Maybe I'm missing something?
Thanks
Tobias
--
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-25 15:35 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 [this message]
2009-03-25 23:26 ` Hamish Moffatt
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=49CA4F52.705@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