qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Roy Tam <roytam@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [BREAKAGE] commit 9bc6304c156dcc01c619672ca33d7152bb18bcb9 breaks build
Date: Fri, 2 Apr 2010 20:16:21 +0800	[thread overview]
Message-ID: <p2x473191351004020516ie46a703az6f42e3df14cba87f@mail.gmail.com> (raw)
In-Reply-To: <r2yf085eb031004020515je593d880j8a5eb9103b36f96f@mail.gmail.com>

2010/4/2 Anthony Liguori <anthony@codemonkey.ws>:
> Try doing a clean build

This is a fresh checkout.

>
> On Apr 2, 2010 4:43 AM, "Roy Tam" <roytam@gmail.com> wrote:
>
> Config:
>
> Install prefix    c:/Program Files/Qemu
> BIOS directory    c:/Program Files/Qemu
> binary directory  c:/Program Files/Qemu
> Source path       /usr/home/User/qemu
> C compiler        gcc
> Host C compiler   gcc
> CFLAGS            -O2 -g
> QEMU_CFLAGS       -m32 -D__USE_MINGW_ANSI_STDIO=1
> -DWIN32_LEAN_AND_MEAN -DWINVER=0x501 -Wold-style-definition -I.
> -I$(SRC_PATH) -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall
> -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes
> -fno-strict-aliasing
> LDFLAGS           -Wl,--warn-common -m32 -g
> make              make
> install           install
> host CPU          i386
> host big endian   no
> target list       i386-softmmu x86_64-softmmu mips64el-softmmu
> tcg debug enabled no
> Mon debug enabled no
> gprof enabled     no
> sparse enabled    no
> strip binaries    yes
> profiler          no
> static build      no
> -Werror enabled   no
> SDL support       yes
> curses support    no
> curl support      no
> check support     no
> mingw32 support   yes
> Audio drivers     sdl
> Extra audio cards ac97 sb16 adlib
> Block whitelist
> Mixer emulation   no
> VNC TLS support   no
> VNC SASL support  no
> xen support       no
> brlapi support    no
> bluez  support    no
> Documentation     yes
> NPTL support      no
> GUEST_BASE        yes
> PIE user targets  no
> vde support       no
> IO thread         no
> Linux AIO support no
> Install blobs     yes
> KVM support       no
> fdt support       no
> preadv support    no
> fdatasync         no
> uuid support      no
> vhost-net support no
>
> Error log:
>  LINK  i386-softmmu/qemu.exe
> virtio-net.o: In function `virtio_net_reset':
> C:/msys/home/User/qemu/hw/virtio-net.c:122: undefined reference to
> `tap_get_vhost_net'
> virtio-net.o: In function `virtio_net_get_features':
> C:/msys/home/User/qemu/hw/virtio-net.c:187: undefined reference to
> `tap_get_vhost_net'
> C:/msys/home/User/qemu/hw/virtio-net.c:190: undefined reference to
> `tap_get_vhost_net'
> virtio-net.o: In function `virtio_net_save':
> C:/msys/home/User/qemu/hw/virtio-net.c:719: undefined reference to
> `tap_get_vhost_net'
> virtio-net.o: In function `virtio_net_set_status':
> C:/msys/home/User/qemu/hw/virtio-net.c:863: undefined reference to
> `tap_get_vhost_net'
> virtio-net.o:C:/msys/home/User/qemu/hw/virtio-net.c:870: more
> undefined references to `tap_get_vhost_net' follow
> collect2: ld returned 1 exit status
> make[1]: *** [qemu.exe] Error 1
> make: *** [subdir-i386-softmmu] Error 2
>
>
>

  reply	other threads:[~2010-04-02 12:16 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 [this message]
2010-04-02 14:09     ` Blue Swirl
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=p2x473191351004020516ie46a703az6f42e3df14cba87f@mail.gmail.com \
    --to=roytam@gmail.com \
    --cc=anthony@codemonkey.ws \
    --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).