On 30/11/07 05:16 +0800, thisway.diy wrote: > Hi, all! > When I was running "sb2-init ARM > /work/tools/arm-2007q3/bin/arm-none-linux-gnueabi-gcc", > there are some error, the log are: > " > checking whether the C compiler works... configure: error: cannot run C > compiled programs. > If you meant to cross compile, use `--host'. > See `config.log' for more details. > Running /work/scratchbox2/bin/sb2-build-libtool failed > " > > In config.log, I can see the informaton below: > " > configure:2830: checking whether the C compiler works > configure:2836: ./a.out > qemu: Unsupported syscall: 983045 > cannot set up thread-local storage: unknown error
This is due to incomplete EABI support in qemu for user-mode emulation. > I have install qemu-0.9.0+20070816-1, and it runs well: > I can use "qemu-arm /work/nfs_root/fs_qtopia/bin/busybox" to run the arm > application on x86. > > But in sb2, /work/nfs_root/fs_qtopia/bin/busybox can't run directly: > " > [SB2] [EMAIL PROTECTED] /work/scratchbox2/fs_x $ > /work/nfs_root/fs_qtopia/bin/busybox > bash: /work/nfs_root/fs_qtopia/bin/busybox: No such file or directory > =======> it can't run > > [SB2] [EMAIL PROTECTED] /work/scratchbox2/fs_x $ qemu-arm > /work/nfs_root/fs_qtopia/bin/busybox > BusyBox v1.7.0 (2007-10-01 19:24:24 CST) multi-call binary > ========> it is ok > " > > I can run the ARM application in sb2 directly, is it true ? > Thank you evry much, please give me some suggestions. > Is the qemu-arm binary the same? You can see exactly which binary sb2 is using from $HOME/.scratchbox2/YOURTARGET/sb2.config, look for the SBOX_CPUTRANSPARENCY_METHOD line. You may want to also run sb2 with -d switch, you'll get a debug output into $HOME/sb2_mapping_*.log, that might give a hint of what's going wrong. /lauri _______________________________________________ Scratchbox-devel mailing list [email protected] http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-devel
