From: Blue Swirl <blauwirbel@gmail.com>
To: Roy Tam <roytam@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [BREAKAGE] commit 9bc6304c156dcc01c619672ca33d7152bb18bcb9 breaks build
Date: Fri, 2 Apr 2010 17:09:48 +0300 [thread overview]
Message-ID: <h2xf43fc5581004020709k4ce41a1bxf93ef86cb12da493@mail.gmail.com> (raw)
In-Reply-To: <p2x473191351004020516ie46a703az6f42e3df14cba87f@mail.gmail.com>
On 4/2/10, Roy Tam <roytam@gmail.com> wrote:
> 2010/4/2 Anthony Liguori <anthony@codemonkey.ws>:
>
> > Try doing a clean build
>
>
> This is a fresh checkout.
I can confirm this with mingw32:
LINK sparc64-softmmu/qemu-system-sparc64.exe
virtio-net.o: In function `virtio_net_exit':
/src/qemu/hw/virtio-net.c:943: undefined reference to `_tap_get_vhost_net'
virtio-net.o: In function `virtio_net_save':
/src/qemu/hw/virtio-net.c:719: undefined reference to `_tap_get_vhost_net'
virtio-net.o: In function `virtio_net_reset':
/src/qemu/hw/virtio-net.c:122: undefined reference to `_tap_get_vhost_net'
virtio-net.o: In function `virtio_net_set_status':
/src/qemu/hw/virtio-net.c:863: undefined reference to `_tap_get_vhost_net'
/src/qemu/hw/virtio-net.c:870: undefined reference to `_tap_get_vhost_net'
virtio-net.o:/src/qemu/hw/virtio-net.c:878: more undefined references
to `_tap_get_vhost_net' follow
collect2: ld returned 1 exit status
next prev parent reply other threads:[~2010-04-02 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 9:38 [Qemu-devel] [BREAKAGE] commit 9bc6304c156dcc01c619672ca33d7152bb18bcb9 breaks build Roy Tam
2010-04-02 12:15 ` Anthony Liguori
2010-04-02 12:16 ` Roy Tam
2010-04-02 14:09 ` Blue Swirl [this message]
2010-04-02 14:30 ` Stefan Weil
2010-04-02 15:27 ` Anthony Liguori
2010-04-02 15:41 ` Anthony Liguori
2010-04-04 10:31 ` Michael S. Tsirkin
2010-04-04 10:35 ` Roy Tam
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=h2xf43fc5581004020709k4ce41a1bxf93ef86cb12da493@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roytam@gmail.com \
/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).