From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=57955 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQajp-0004GV-A0 for qemu-devel@nongnu.org; Thu, 09 Dec 2010 02:16:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PQajo-0003xr-2j for qemu-devel@nongnu.org; Thu, 09 Dec 2010 02:16:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47804) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PQajn-0003xf-Oj for qemu-devel@nongnu.org; Thu, 09 Dec 2010 02:16:23 -0500 Message-ID: <4D008246.9070500@redhat.com> Date: Thu, 09 Dec 2010 08:16:22 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <4CFF6E8F.7000300@gmail.com> <1291812551-12590-1-git-send-email-pbonzini@redhat.com> <4CFFFC1A.1090001@gmail.com> In-Reply-To: <4CFFFC1A.1090001@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] fix qruncom compilation problems List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Bonifazi Cc: qemu-devel@nongnu.org On 12/08/2010 10:43 PM, Stefano Bonifazi wrote: > I've linked qemu-malloc.o and cutils.o together with qruncom.c and I > managed to succesfully make it! > here the make line: >> #$(MAKE) -C ../i386-linux-user libqemu.a >> $(CC) $(CFLAGS) -fomit-frame-pointer $(LDFLAGS) -I../target-i386 -I.. >> -I../linux-user -I../i386-linux-user -I../fpu \ >> -o $@ ../qemu-malloc.o ../cutils.o $(filter %.c, $^) >> -L../i386-linux-user -lqemu -lm > > Anyway running it with a com file as argument gave the error: >> mmap: Operation not permitted > I think the problem is with "MAP_FIXED" parameter in mmap > (http://opengroup.org/onlinepubs/007908799/xsh/mmap.html) having chosen > 0x00000000 as starting address.. but it is pretty difficult for me atm > to understand it, I've never used this function before and I am a > beginner in these topics > Removing that parameter mmap succeeds, but then I get "segmentation > fault" in cpu_init You have to run it as root I think. Paolo