From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Filip Navara <filip.navara@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] compile failure: undefined reference to `__mingw_vfprintf'
Date: Sun, 5 Jul 2009 21:12:22 +0200 [thread overview]
Message-ID: <D41DC54ACC224E6D9275A291F503EE11@FSCPC> (raw)
In-Reply-To: <5b31733c0906281525u2b248409me0ad0190b7e00cec@mail.gmail.com>
Filip Navara wrote:
> Sebastian Herbszt wrote:
>> $ make
>> LINK i386-softmmu/qemu.exe
>> c:/Programme/MinGW/lib/libSDLmain.a(SDL_win32_main.o):(.text+0x1b):
>> undefined reference to `__mingw_vfprintf'
>> collect2: ld returned 1 exit status
>> make[1]: *** [qemu.exe] Error 1
>> make: *** [subdir-i386-softmmu] Error 2
>>
>> 537fe2d63f744e7c96ff45b60d09486a81958e06 is first bad commit
>> commit 537fe2d63f744e7c96ff45b60d09486a81958e06
>> Author: Anthony Liguori <aliguori@us.ibm.com>
>> Date: Tue Jun 16 15:17:22 2009 -0500
>>
>> Make sure to use SDL_CFLAGS everywhere we include SDL headers
>>
>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>>
>> - Sebastian
>>
>
> Seems to be a bug in your MinGW installation, the function should be
> implemented in libmingwex.a. I'm using mingw runtime 3.15.2 and
> everything links just fine.
After the upgrade to 3.15.2 it does indeed link fine. But it seems the commit
broke output to console:
> qemu-3f9a.exe -net nic,model=blub
Warning: vlan 0 is not connected to host network
Could not open '\\.\kqemu' - QEMU acceleration layer not activated: 2
qemu: Unsupported NIC model: blub
qemu: Supported NIC models: ne2k_pci,i82551,i82557b,i82559er,rtl8139,e1000,pcnet,virtio
> qemu-537f.exe -net nic,model=blub
(no output here)
- Sebastian
next prev parent reply other threads:[~2009-07-05 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 21:24 [Qemu-devel] compile failure: undefined reference to `__mingw_vfprintf' Sebastian Herbszt
2009-06-28 22:25 ` Filip Navara
2009-07-04 21:21 ` Sebastian Herbszt
2009-07-05 19:12 ` Sebastian Herbszt [this message]
2009-07-05 19:56 ` Filip Navara
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=D41DC54ACC224E6D9275A291F503EE11@FSCPC \
--to=herbszt@gmx.de \
--cc=filip.navara@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.