From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003274]: Package Python broken
Date: Wed, 7 May 2008 12:39:25 -0700 [thread overview]
Message-ID: <a328de13c8ed416ea4c0d931b5d36eae@bugs.uclibc.org> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=3274
======================================================================
Reported By: roeme
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3274
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 05-07-2008 11:01 PDT
Last Modified: 05-07-2008 12:39 PDT
======================================================================
Summary: Package Python broken
Description:
When trying to include the python package, the build process fails with the
following error:
make[1]: Leaving directory
`/home/roeme/minim/buildroot/buildroot/build_i586/Python-2.4.2'
/bin/sh: line 8: -/usr/bin/make: No such file or directory
make: ***
[/home/roeme/minim/buildroot/buildroot/build_i586/Python-2.4.2/.hostpython]
Error 127
Enabling "Development Files on target" or removing modules marked as
"unusual" (curses/unicodedata) does not help as well as reducing the
number of jobs to run simultaneously.
======================================================================
----------------------------------------------------------------------
bernhardf - 05-07-08 11:37
----------------------------------------------------------------------
Thy pyhon package wants a big cleanup anyway:
- unpack into one location (I'd use the TOOL_BUIDDIR)
- build python-host (why is that needed anyway?) into
(TOOL_BUILDDIR)/$(PYTHON_DIR)-host
- build python in $(BUILD_DIR)
----------------------------------------------------------------------
roeme - 05-07-08 12:28
----------------------------------------------------------------------
How can I help? Or what must one do to get the package working?
I'll dive into the docs now. Maybe I'll get something working, I wanted to
get accustomed to buildroot's internals anyway, to add sw by myself.
However, I'm a bloody novice, so any help on this bug is GREATLY
appreciated. Since I'm in a thight schedule, it might take several months
before I even have a clue how to fix it, whereas you guys probably only
need one day.
There's a typo in the submission, by host system I meant build system.
----------------------------------------------------------------------
roeme - 05-07-08 12:39
----------------------------------------------------------------------
Python seems to have cross-compilation support (see also:
http://mail.python.org/pipermail/patches/2004-October/016312.html )
However, it's not used:
(snip)
checking whether we are cross compiling... no
(/snip)
(I might be off-track here, but maybe this is of some use to the
developers)
Issue History
Date Modified Username Field Change
======================================================================
05-07-08 11:01 roeme New Issue
05-07-08 11:01 roeme Status new => assigned
05-07-08 11:01 roeme Assigned To => buildroot
05-07-08 11:37 bernhardf Note Added: 0007474
05-07-08 12:04 roeme Note Added: 0007484
05-07-08 12:28 roeme Note Edited: 0007484
05-07-08 12:39 roeme Note Added: 0007494
======================================================================
next reply other threads:[~2008-05-07 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 19:39 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-09 10:07 [Buildroot] [buildroot 0003274]: Package Python broken bugs at busybox.net
2008-05-09 7:17 bugs at busybox.net
2008-05-07 19:04 bugs at busybox.net
2008-05-07 18:37 bugs at busybox.net
2008-05-07 18:01 bugs at busybox.net
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=a328de13c8ed416ea4c0d931b5d36eae@bugs.uclibc.org \
--to=bugs@busybox.net \
--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