From: Consul <void@aleksoft.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v6
Date: Fri, 27 Mar 2009 13:27:29 -0700 [thread overview]
Message-ID: <49CD36B1.5060506@aleksoft.net> (raw)
In-Reply-To: <f43fc5580903271303l77e871a9g44007bcb7e217295@mail.gmail.com>
Blue Swirl wrote:
> Hi,
>
> In this version only the script invocation has been changed.
>
> I still wonder if this is OK for Windows, please test.
No.
c:/test/qemu/vl.c: In function `main':
c:/test/qemu/vl.c:4663: error: `QEMU_OPTION_k' undeclared (first use in this function)
c:/test/qemu/vl.c:4663: error: (Each undeclared identifier is reported only once
c:/test/qemu/vl.c:4663: error: for each function it appears in.)
c:/test/qemu/vl.c:4842: error: `QEMU_OPTION_daemonize' undeclared (first use in this function)
c:/test/qemu/vl.c:4933: error: `QEMU_OPTION_chroot' undeclared (first use in this function)
c:/test/qemu/vl.c:4936: error: `QEMU_OPTION_runas' undeclared (first use in this function)
c:/test/qemu/vl.c:5146: warning: implicit declaration of function `dma_helper_init'
c:/test/qemu/vl.c:4269: warning: unused variable `pwd'
make[1]: *** [vl.o] Error 1
make[1]: Leaving directory `/c/test/qemu/i386-softmmu'
make: *** [subdir-i386-softmmu] Error 2
next prev parent reply other threads:[~2009-03-27 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 20:03 [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v6 Blue Swirl
2009-03-27 20:27 ` Consul [this message]
2009-03-27 20:52 ` [Qemu-devel] " Blue Swirl
2009-03-27 21:11 ` Consul
2009-03-28 6:23 ` Blue Swirl
2009-03-27 20:33 ` Consul
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=49CD36B1.5060506@aleksoft.net \
--to=void@aleksoft.net \
--cc=qemu-devel@nongnu.org \
/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).