Thomas Petazzoni wrote:
As far as I've understood, and my experiments tend to confirm this, the
toolchain must have been generated in a /scratchbox/compilers/
directory in order to be integrated into Scratchbox. Moreover, the
toolchain must be compiled against the Scratchbox environment, notably
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
SBOX_REDIRECT_IGNORE=/usr/local/bin/python.
However when I type 'python' I still get ve
Thomas Petazzoni wrote:
I tried to integrate an ARM and MIPS toolchain, generated by Buildroot,
into Scratchbox using sb-toolchain-extras. These toolchains have been
successfully integrated, and they are able to generate binaries that
can be transparently executed by Scratchbox.
However, at the
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
>> SBOX_REDIRECT_IGNORE=/usr/loca
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, it
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_u
