From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Bonifazi <stefboombastic@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] fix qruncom compilation problems
Date: Thu, 09 Dec 2010 08:16:22 +0100 [thread overview]
Message-ID: <4D008246.9070500@redhat.com> (raw)
In-Reply-To: <4CFFFC1A.1090001@gmail.com>
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
next prev parent reply other threads:[~2010-12-09 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 11:39 [Qemu-devel] Compiling tests/qruncom.c Stefano Bonifazi
2010-12-08 12:49 ` [Qemu-devel] [PATCH] fix qruncom compilation problems Paolo Bonzini
2010-12-08 21:43 ` [Qemu-devel] " Stefano Bonifazi
2010-12-09 7:16 ` Paolo Bonzini [this message]
2010-12-09 17:29 ` Stefano Bonifazi
2010-12-10 8:53 ` Paolo Bonzini
2010-12-10 21:43 ` Stefano Bonifazi
[not found] ` <4D02A030.6080400@redhat.com>
2010-12-11 14:42 ` [Qemu-devel] " Stefano Bonifazi
2010-12-13 8:27 ` [Qemu-devel] " Paolo Bonzini
2010-12-09 3:32 ` [Qemu-devel] " Isaku Yamahata
2010-12-09 7:16 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D008246.9070500@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefboombastic@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).