From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] No rule to make target ../libhw32/virtio.o
Date: Thu, 13 Jan 2011 15:24:53 +0000 [thread overview]
Message-ID: <4D2F1945.6020000@siriusit.co.uk> (raw)
In-Reply-To: <4D2F15B0.7090209@loskot.net>
On 13/01/11 15:09, Mateusz Loskot wrote:
> Hi,
>
> I'm building current Git master (SHA1:facf1a60) using latest MingW32
> on Windows Vista and compilation fails with the following error:
>
> g:/src/qemu/_git/master/disas.c: In function 'generic_print_address':
> g:/src/qemu/_git/master/disas.c:65:5: warning: 'I' flag used with '%x'
> gnu_printf format
> g:/src/qemu/_git/master/disas.c:65:5: warning: format '%I64x' expects
> type 'unsigned int', but argument 3 has type 'bfd_vma'
> make[1]: *** No rule to make target `../libhw32/virtio.o', needed by
> `qemu.exe'. Stop.
> make: *** [subdir-i386-softmmu] Error 2
Hi Mateusz,
Good to hear from you again. On a separate note, as a Windows user have
you tried using the mingw-w64 compiler
(http://mingw-w64.sourceforge.net/) to build qemu instead?
While the name suggests only a 64-bit compiler, the basic installation
consists of both 32 and 64 bit compilers, plus the team there are
currently very active and in my experience a lot more responsive when it
comes to fixing any problems that may arise.
HTH,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
next prev parent reply other threads:[~2011-01-13 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 15:09 [Qemu-devel] No rule to make target ../libhw32/virtio.o Mateusz Loskot
2011-01-13 15:24 ` Mark Cave-Ayland [this message]
2011-01-13 16:09 ` Mateusz Loskot
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=4D2F1945.6020000@siriusit.co.uk \
--to=mark.cave-ayland@siriusit.co.uk \
--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).