Le Tue, 9 Sep 2008 14:45:52 -0700, "L A" <[EMAIL PROTECTED]> a écrit :
> For your problem: you might want to check the environment variables > and symbolic links under your scratchbox home directory. Which one should I check specifically ? The same Scratchbox installation works perfectly with an official Scratchbox toolchain. > And I have a question for you: I never got the scratchbox to run mips > binaries (neither with qemu or sbrsh). How did you got it work? I did nothing special: configure a target for mips, select Qemu as the CPU transparency method, and voila. It just worked. Scratchbox by default already configures mips as a supported platform with regard to the binfmt_misc facility: $ ls /proc/sys/fs/binfmt_misc/ jar register sbox-cris sbox-powerpc sbox-win openjdk-6 sbox-arm sbox-mips sbox-sh status python2.5 sbox-armeb sbox-mipsel sbox-sparc wine $ cat /proc/sys/fs/binfmt_misc/sbox-mips enabled interpreter /scratchbox/tools/bin/misc_runner flags: P offset 0 magic 7f454c4600020000000000000000000000000008 mask ffffffff00ff000000000000000000000000ffff Sincerly, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers and embedded Linux development, consulting, training and support. http://free-electrons.com _______________________________________________ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users