From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hamish Moffatt Date: Thu, 8 May 2008 10:27:16 +1000 Subject: [Buildroot] buildroot - python problem In-Reply-To: <079f01c8b054$166a3620$060514ac@atmel.com> References: <223E6519BDCAC74695BEE9D163F8E6592218AB@oakleaf10.oakleafconsultancy.com> <079f01c8b054$166a3620$060514ac@atmel.com> Message-ID: <20080508002716.GB5014@cloud.net.au> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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