From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] master doesn't build on mingw32
Date: Fri, 05 Aug 2011 12:57:32 +0200 [thread overview]
Message-ID: <4E3BCC9C.6040805@siemens.com> (raw)
In-Reply-To: <4E3BBE80.10104@redhat.com>
On 2011-08-05 11:57, Gerd Hoffmann wrote:
> CC slirp/arp_table.o
> /home/kraxel/projects/qemu/slirp/arp_table.c: In function 'arp_table_add':
> /home/kraxel/projects/qemu/slirp/arp_table.c:29: error: expected '=',
> ',', ';', 'asm' or '__attribute__' before 'broadcast_addr'
> /home/kraxel/projects/qemu/slirp/arp_table.c:29: error: 'broadcast_addr'
> undeclared (first use in this function)
> /home/kraxel/projects/qemu/slirp/arp_table.c:29: error: (Each undeclared
> identifier is reported only once
> /home/kraxel/projects/qemu/slirp/arp_table.c:29: error: for each
> function it appears in.)
> /home/kraxel/projects/qemu/slirp/arp_table.c: In function
> 'arp_table_search':
> /home/kraxel/projects/qemu/slirp/arp_table.c:66: error: expected '=',
> ',', ';', 'asm' or '__attribute__' before 'broadcast_addr'
> /home/kraxel/projects/qemu/slirp/arp_table.c:66: error: 'broadcast_addr'
> undeclared (first use in this function)
> gmake: *** [slirp/arp_table.o] Error 1
>
Missed that. My mingw32 toolchain is usually not working (comes without
liberity). Will send a pull request for a fix.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2011-08-05 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 9:57 [Qemu-devel] master doesn't build on mingw32 Gerd Hoffmann
2011-08-05 10:57 ` Jan Kiszka [this message]
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=4E3BCC9C.6040805@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kraxel@redhat.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 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).