On Thu, Apr 15, 2010 at 9:33 AM, Blue Swirl <blauwir...@gmail.com> wrote: > On 4/15/10, David Munday <cro...@soe.ucsc.edu> wrote: >> Hello, >> Our lab just did a pull from the qemu repository and now we are unable to >> run a 32-bit sparc target on a 64-bit host. This functionality was working >> before we did the pull. The error message we get is:mmap: No such device or >> address >> >> And then the process dies. We are not sure why this is occuring but have >> verified against our earlier qemu copy that the behavior did not exist >> before our pull on Sunday. >> >> We appreciate any insights anyone might have. > > I can't replicate this, sparc-linux-user, sparc32plus-linux-user and > sparc64-linux-user still work like before on amd64 Linux host. > > What is the host and which program? Could you bisect the problem, > there haven't been that many commits in last few days? >
I have also noticed that sparc-linux-user does not compile on an AMD64 host (CentOS 5.4): cc1: warnings being treated as errors /mada/users/gsouther/projs/qemu/linux-user/mmap.c: In function ‘mmap_find_vma’: /mada/users/gsouther/projs/qemu/linux-user/mmap.c:367: warning: comparison is always false due to limited range of data type make[1]: *** [mmap.o] Error 1 gmake: *** [subdir-sparc-linux-user] Error 2 The compilation warning can be fixed by removing the ul specifier from -1ul, but I'm wondering if you had noticed the same problem. -Gabriel
