From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot - python problem
Date: Thu, 8 May 2008 10:27:16 +1000 [thread overview]
Message-ID: <20080508002716.GB5014@cloud.net.au> (raw)
In-Reply-To: <079f01c8b054$166a3620$060514ac@atmel.com>
On Wed, May 07, 2008 at 05:07:18PM +0200, Ulf Samuelsson wrote:
> The python.mk looks pretty unclean to me.
> Should not the host python be built in the toolchain directory,
> and the result moved to STAGING_DIR?
> Then it could be easily be used for other stuff as well.
I'm using the python package here and never saw the problem reported in
this thread. Your suggestion of installing properly into $STAGING_DIR
seems reasonable though.
I am planning to update the package for Python 2.5 soon so I will fix
that up at the same time. Next week hopefully.
Changing versions might break some people's code, so it may be necessary
to support multiple versions and allow the user to choose. Do you other
Python users have any comments on this?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-05-08 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 9:48 [Buildroot] buildroot - python problem Richard Hardy
2008-05-07 14:34 ` Andrew Dyer
2008-05-07 15:07 ` Ulf Samuelsson
2008-05-08 0:27 ` Hamish Moffatt [this message]
2008-05-08 0:31 ` Ulf Samuelsson
2008-05-08 0:58 ` Hamish Moffatt
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=20080508002716.GB5014@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