On Thu, 3 Apr 2008, Jos? Lu?s wrote: > Yes, rebuilding qemu with arm-eabi patches ( > http://qemu-arm-eabi.wiki.sourceforge.net/) will fix this problem. And sorry > because the link that I passed to you was in portuguese. - tried reading with Babelfish; not so bad, but this is better :-) > But the steps are simple: > > 1. You have to install gcc-3.4 and zlib1g-dev > - (sudo apt-get install gcc-3.4 zlib1g-dev) No compat-gcc-3.4 for my Fedora Core 4; I had compat-gcc-3.2 .. I forced in 3.4 from FC6 .. seems to work, but still gave the FUTEX error etc. below. Maybe 3.2 would have worked equally.. Also had to install SDL-devel > 2. Get the patched qemu-arm-eabi sources available in > http://sourceforge.net/projects/qemu-arm-eabi/ > - svn co > https://qemu-arm-eabi.svn.sourceforge.net/svnroot/qemu-arm-eabi/trunkqemu-arm-eabi > 3. Compile > - cd qemu-arm-eabi > - ./configure --target-list=arm-linux-user --static > - make I had errors compiling linux-user/syscall.c: 59:25: warning: sys/inotify.h: No such file 409: undefined reference to `inotify_rm_watch' 3311: error: `FUTEX_LOCK_PI' undeclared I commented out the conditional code for inotify_rm_watch etc. and removed the check for FUTEX_LOCK_PI (leave FUTEX_WAIT) and it "seems to work". > 4. Update the scratchbox > - sudo cp arm-linux-user/qemu-arm > /scratchbox/devkits/cputransp/bin/qemu-arm-eabi-sb2 > - sudo vim /scratchbox/devkits/cputransp/etc/cputransp-methods > - add the line: qemu-arm-eabi-sb2 > - vim /scratchbox/users/USERNAME/targets/SDK_ARMEL.config > - change the variable value SBOX_CPUTRANSPARENCY_METHOD to > /scratchbox/devkits/cputransp/bin/qemu-arm-eabi-sb2 I have CHINOOK_ARMEL.config not SDK_ARMEL.config > > The syscall errors will disappear. Yes :-) (have not tried running the code .. various other dependencies to be resolved first ..) Andrew
