From: "Natalia Portillo" <claunia@claunia.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Problem compiling under mingw32
Date: Sat, 3 Jul 2004 20:10:17 +0100 [thread overview]
Message-ID: <E1BgpvE-0000wB-4v@lists.gnu.org> (raw)
In-Reply-To: <40E6FC39.9060205@aol.com>
When I try to compile the lastest CVS QEMU from mingw32
qemu-system-ppc-softmmu shows an error (attached below), and the
qemu-system-i386-softmmu only shows standard output (help and monitor) when
running under MSYS, under the win32 command line it shows nothing.
Any idea?
$ make
for d in i386-softmmu ppc-softmmu; do \
make -C $d all || exit 1 ; \
done
make[1]: Entering directory `/home/Claunia/qemu/i386-softmmu'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/Claunia/qemu/i386-softmmu'
make[1]: Entering directory `/home/Claunia/qemu/ppc-softmmu'
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I.
-I/home/Claunia/qemu/target-ppc -I/home/Claunia/qemu -D_GNU_SOURCE -c -o
vl.o /home/Claunia/qemu/vl.c
In file included from c:/ARCHIV~1/MingW/include/windef.h:246,
from c:/ARCHIV~1/MingW/include/windows.h:48,
from C:/Archivos de
programa/MinGW/MSYS/home/Claunia/qemu/vl.c:60:
c:/ARCHIV~1/MingW/include/winnt.h:97: parse error before numeric constant
C:/Archivos de programa/MinGW/MSYS/home/Claunia/qemu/vl.c:1205: warning:
`term_exit' defined but not used
make[1]: *** [vl.o] Error 1
make[1]: Leaving directory `/home/Claunia/qemu/ppc-softmmu'
make: *** [all] Error 1
next prev parent reply other threads:[~2004-07-03 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 18:34 [Qemu-devel] more OS X patch help Fred Hope
2004-07-03 19:10 ` Natalia Portillo [this message]
2004-07-03 19:12 ` [Qemu-devel] Problem compiling under mingw32 Filip Navara
2004-07-04 5:25 ` kazu
2004-07-03 21:13 ` [Qemu-devel] more OS X patch help Jeff Cooper
-- strict thread matches above, loose matches on Subject: below --
2004-07-03 19:40 [Qemu-devel] Problem compiling under mingw32 claunia
2004-07-03 19:54 ` J. Mayer
2004-07-03 20:05 Natalia Portillo
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=E1BgpvE-0000wB-4v@lists.gnu.org \
--to=claunia@claunia.com \
--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).