* [Qemu-devel] cvs build broken?
@ 2005-06-10 23:06 jeebs
2005-06-11 10:25 ` Oliver Gerlich
0 siblings, 1 reply; 3+ messages in thread
From: jeebs @ 2005-06-10 23:06 UTC (permalink / raw)
To: Qemu mailing list
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] cvs build broken?
2005-06-10 23:06 [Qemu-devel] cvs build broken? jeebs
@ 2005-06-11 10:25 ` Oliver Gerlich
2005-06-11 14:53 ` jeebs
0 siblings, 1 reply; 3+ messages in thread
From: Oliver Gerlich @ 2005-06-11 10:25 UTC (permalink / raw)
To: qemu-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
maybe it's the same problem as mentioned here:
http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00077.html
Could you try the patch given there?
Good luck,
Oliver Gerlich
jeebs@yango.us wrote:
> 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.
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCqrwRTFOM6DcNJ6cRAqJaAJ0VOjW1sYM9DZhIiwvoJPmYACSV8QCggjs4
wjl7k3A9GedVM64eXNuOH/M=
=Li5J
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] cvs build broken?
2005-06-11 10:25 ` Oliver Gerlich
@ 2005-06-11 14:53 ` jeebs
0 siblings, 0 replies; 3+ messages in thread
From: jeebs @ 2005-06-11 14:53 UTC (permalink / raw)
To: qemu-devel
>"Oliver Gerlich"
> Hi,
> maybe it's the same problem as mentioned here:
> http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00077.html
>
> Could you try the patch given there?
That's it. Thanks.
I don't always get all of the mailing list messages. (Of course, it's
better than my ISP's mail address. It despises mailing lists of any sort.)
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-06-11 15:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-10 23:06 [Qemu-devel] cvs build broken? jeebs
2005-06-11 10:25 ` Oliver Gerlich
2005-06-11 14:53 ` jeebs
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).