From: klondike <franxisco1988@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Nikola Ciprich <extmaillist@linuxbox.cz>,
kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] qemu-kvm: Fix non-PCI target build
Date: Wed, 23 Feb 2011 09:37:43 +0100 [thread overview]
Message-ID: <4D64C757.2070907@gmail.com> (raw)
In-Reply-To: <4D64C545.3020205@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2721 bytes --]
El 23/02/11 09:28, Jan Kiszka escribió:
> On 2011-02-23 09:05, klondike wrote:
>> El 23/02/11 08:49, Nikola Ciprich escribió:
>>> Hello Avi,
>> Hi,
>>> when trying to compile(link) various targets, I get:
>>> LINK sparc-softmmu/qemu-system-sparc
>>> pci-stub.o: In function `do_pci_info_print':
>>> /usr/src/redhat/BUILD/qemu-kvm-0.14.0/hw/pci-stub.c:36: multiple definition of `do_pci_info_print'
>>> pci.o:/usr/src/redhat/BUILD/qemu-kvm-0.14.0/hw/pci.c:1398: first defined here
>>> /usr/bin/ld: Warning: size of symbol `do_pci_info_print' changed from 147 in pci.o to 50 in pci-stub.o
>>> pci-stub.o: In function `do_pci_info':
>>> /usr/src/redhat/BUILD/qemu-kvm-0.14.0/hw/pci-stub.c:31: multiple definition of `do_pci_info'
>>> pci.o:/usr/src/redhat/BUILD/qemu-kvm-0.14.0/hw/pci.c:1560: first defined here
>>> /usr/bin/ld: Warning: size of symbol `do_pci_info' changed from 150 in pci.o to 50 in pci-stub.o
>>> pci.o: In function `pci_update_mappings':
>>> pci.c:(.text+0xa91): undefined reference to `pci_bridge_get_base'
>>> pci.c:(.text+0xaa5): undefined reference to `pci_bridge_get_limit'
>>> pci.c:(.text+0xb7b): undefined reference to `pci_bridge_get_base'
>>> pci.c:(.text+0xb8e): undefined reference to `pci_bridge_get_limit'
>>> pci.o: In function `pci_get_devices_list':
>>> pci.c:(.text+0x2024): undefined reference to `pci_bridge_get_limit'
>>> pci.c:(.text+0x2036): undefined reference to `pci_bridge_get_base'
>>> pci.c:(.text+0x2043): undefined reference to `pci_bridge_get_limit'
>>> pci.c:(.text+0x2050): undefined reference to `pci_bridge_get_base'
>>> pci.c:(.text+0x2060): undefined reference to `pci_bridge_get_limit'
>>> pci.c:(.text+0x2070): undefined reference to `pci_bridge_get_base'
>>> collect2: ld returned 1 exit status
>>> make[1]: *** [qemu-system-sparc] Error 1
>>> make: *** [subdir-sparc-softmmu] Error 2
>> I hit this problem too and after a long night I tracked it back to some
>> odd merge, this patch solved the issue for me.
> This unfortunately breaks the build with device assignment enabled.
> Patch below is required.
>
> Generally, I would recommend to avoid using the qemu-kvm tree for
> anything else than x86 with kvm support. Other use cases ought to work
> but are rarely tested. Better pick upstream qemu in this case until we
> reduced the diffs between both trees to a much smaller amount.
> qemu-kvm-0.15 may become a milestone in this regard.
>
> Jan
Thanks Jan,
Gentoo users have little to no choice until as the qemu and qemu-kvm
ebuilds block each other (so it is impossible to install both at the
same time).
I'll send this patch to the bump request in the gentoo bugzilla if you
agree :D
klondike
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-02-23 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 17:14 [ANNOUNCE] qemu-kvm-0.14.0 Avi Kivity
2011-02-23 7:49 ` Nikola Ciprich
2011-02-23 8:05 ` klondike
2011-02-23 8:16 ` Nikola Ciprich
2011-02-23 8:29 ` Nikola Ciprich
2011-02-23 8:39 ` klondike
2011-04-29 8:59 ` Bharat Bhushan
2011-02-23 8:28 ` [PATCH] qemu-kvm: Fix non-PCI target build Jan Kiszka
2011-02-23 8:37 ` klondike [this message]
2011-02-27 11:35 ` Avi Kivity
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=4D64C757.2070907@gmail.com \
--to=franxisco1988@gmail.com \
--cc=avi@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).