From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] win32 again
Date: Fri, 06 Aug 2004 01:03:46 +0200 [thread overview]
Message-ID: <pan.2004.08.05.23.03.37.696316@reply.to> (raw)
Hi,
I have tied to compare the make output with both linux and win32 build.
I have the same binutils (2.15) and gcc (3.2.3) and have configured only
for i386-softmmu and ppc-softmmu
for win: ./configure --enable-mingw32 --cross-prefix=i386-mingw32-
for linux: ./configure --prefix=/usr --target-list="i386-softmmu
ppc-softmmu"
Win:
i386-mingw32-gcc -DQEMU_TOOL -Wall -O2 -g -fno-strict-aliasing -fpack-struct -g -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -o qemu-img.exe qemu-img.c block.c block-cow.c block-qcow.c aes.c block-vmdk.c -lz -lmingwex
In file included from vl.h:66,
from qemu-img.c:24:
osdep.h:31: warning: `struct siginfo' declared inside parameter list
osdep.h:31: warning: its scope is only this definition or declaration, which is
probably not what you want
In file included from vl.h:66,
from block.c:24:
osdep.h:31: warning: `struct siginfo' declared inside parameter list
osdep.h:31: warning: its scope is only this definition or declaration, which is
probably not what you want
In file included from vl.h:66,
from block-qcow.c:24:
osdep.h:31: warning: `struct siginfo' declared inside parameter list
osdep.h:31: warning: its scope is only this definition or declaration, which is
probably not what you want
In file included from vl.h:66,
from aes.c:30:
osdep.h:31: warning: `struct siginfo' declared inside parameter list
osdep.h:31: warning: its scope is only this definition or declaration, which is
probably not what you want
In file included from vl.h:66,
from block-vmdk.c:24:
osdep.h:31: warning: `struct siginfo' declared inside parameter list
osdep.h:31: warning: its scope is only this definition or declaration, which is
probably not what you want
Linux:
gcc -DQEMU_TOOL -Wall -O2 -g -fno-strict-aliasing -g -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -o qemu-img qemu-img.c block.c
block-cow.c block-qcow.c aes.c block-vmdk.c -lz
reply other threads:[~2004-08-05 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pan.2004.08.05.23.03.37.696316@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--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).