Hi,
Thank you all for the answers.
I did compile python 2.5.2 for host (using created host target) and
installed it into /host_usr as Kalle suggested.
Indeed as Daniel mentioned /host_usr is after /devkits in PATH and new
python wasn't invoked when I typed python in the shell.
Thus I added it at
Daniel Bainton wrote:
If that's the case, we have to fix it...
Just do a echo $PATH in SB. I doubt /host_usr is before the devkits
and core for you either. Isn't there a bug for this? Atleast it's been
mentioned in IRC... :)
Fixed in the vcs head.
Yeah, the bugzilla is still offline...
2008/9/22 Jussi Hakala [EMAIL PROTECTED]:
Mateusz Jan Dominikowski wrote:
SB comes with Python version 2.3.4 so I compiled 2.5.2 from sources and
installed it with standard prefix (/usr/local).
As /usr/local/bin is redirected in SB I tried to export
Daniel Bainton wrote:
That, or you can do as Kalle suggested and compile a newer version of python
for the host architecture and put it inside /host_usr/. After that you won't
need any environment variables since stuff in /host_usr/ always override the
stuff in devkits and the core.
That is,
2008/9/22 Jussi Hakala [EMAIL PROTECTED]:
Daniel Bainton wrote:
That, or you can do as Kalle suggested and compile a newer version of
python
for the host architecture and put it inside /host_usr/. After that you
won't
need any environment variables since stuff in /host_usr/ always override
2008/9/12 Mateusz Jan Dominikowski [EMAIL PROTECTED]:
SB comes with Python version 2.3.4 so I compiled 2.5.2 from sources and
installed it with standard prefix (/usr/local).
If you don't want the python to be present in the target filesystem,
you'd better off compiling it as a host tool (with
Hi,
I am using scratchbox to create dedicated linux distribution for small
device with x86 architecture.
The goal is to compile everything (mostly) using only compile from
sources approach.
I installed SB from the following packages:
scratchbox-core-1.0.10-i386.tar.gz
