From: <jeebs@yango.us>
To: Qemu mailing list <Qemu-devel@nongnu.org>
Subject: [Qemu-devel] cvs build broken?
Date: Fri, 10 Jun 2005 18:06:31 -0500 [thread overview]
Message-ID: <001101c56e11$0e711ac0$334d21d1@organiza3bfb0e> (raw)
I've been following the qemu-user's forum thread with CoMiKe describing how
to build qemu under windows with MingW. For those of us who don't use
Linux, the regular instructions are about as clear as mud.
CoMiKe's instructions are pretty good, and as soon as a few more people give
it a try and work out any more bugs, I hope the directions get added to the
official qemu docs.
It looks like there's a compile error for Mingw for the current cvs.
Here's the relevant section.
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I/home/Admin/qemu/target-i386
-I/home/Admin/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/home/Admin/qemu/fpu -I/home/Admin/qemu/slirp -c -o slirp/udp.o
/home/Admin/qemu/slirp/udp.c
H:/MSys/home/Admin/qemu/slirp/udp.c: In function `udp_emu':
H:/MSys/home/Admin/qemu/slirp/udp.c:428: warning: no semicolon at end of
struct or union
H:/MSys/home/Admin/qemu/slirp/udp.c:428: error: syntax error before '.'
token
H:/MSys/home/Admin/qemu/slirp/udp.c:405: warning: unused variable `addrlen'
H:/MSys/home/Admin/qemu/slirp/udp.c:429: warning: unused variable `seqn'
H:/MSys/home/Admin/qemu/slirp/udp.c:430: warning: unused variable `message'
H:/MSys/home/Admin/qemu/slirp/udp.c:431: warning: unused variable
`data_type'
H:/MSys/home/Admin/qemu/slirp/udp.c:432: warning: unused variable `pkt_len'
H:/MSys/home/Admin/qemu/slirp/udp.c: At top level:
H:/MSys/home/Admin/qemu/slirp/udp.c:433: warning: type defaults to `int' in
declaration of `cu_head'
H:/MSys/home/Admin/qemu/slirp/udp.c:433: warning: data definition has no
type or storage class
H:/MSys/home/Admin/qemu/slirp/udp.c:435: error: syntax error before "switch"
H:/MSys/home/Admin/qemu/slirp/udp.c:618: warning: type defaults to `int' in
declaration of `cu_head'
H:/MSys/home/Admin/qemu/slirp/udp.c:618: error: conflicting types for
'cu_head'
H:/MSys/home/Admin/qemu/slirp/udp.c:433: error: previous declaration of
'cu_head' was here
H:/MSys/home/Admin/qemu/slirp/udp.c:618: error: `m' undeclared here (not in
a function)
H:/MSys/home/Admin/qemu/slirp/udp.c:618: warning: data definition has no
type or storage class
H:/MSys/home/Admin/qemu/slirp/udp.c:619: error: syntax error before '->'
token
make[1]: *** [slirp/udp.o] Error 1
make[1]: Leaving directory `/home/Admin/qemu
Plus an assortment of warnings. I would have expected qemu to compile
cleanly.
I tried the cvs version over the past several days, and they fail. The
official 0.70 build compiles, though.
At first I thought I was doing something wrong, since I'm not familiar with
building it. Especially since I would have expected somebody to have
complained by now.
And I've even tried two versions of Mingw/GCC.
But the error is pretty consistant, and the official 0.70 build off qemu.org
compiles and runs.
So I figured I should report it, in case it's a Windows specific problem.
We all know how many windows users there are in here.... And even fewer
trying to build it themselves.
next reply other threads:[~2005-06-10 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 23:06 jeebs [this message]
2005-06-11 10:25 ` [Qemu-devel] cvs build broken? Oliver Gerlich
2005-06-11 14:53 ` jeebs
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='001101c56e11$0e711ac0$334d21d1@organiza3bfb0e' \
--to=jeebs@yango.us \
--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).