From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Gerhard Wiesinger <lists@wiesinger.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Compile/link errors
Date: Fri, 24 Feb 2012 12:24:40 -0600 [thread overview]
Message-ID: <4F47D5E8.1040204@codemonkey.ws> (raw)
In-Reply-To: <4F47D247.3020509@suse.de>
On 02/24/2012 12:09 PM, Andreas Färber wrote:
> Am 24.02.2012 18:27, schrieb Anthony Liguori:
>> On 02/24/2012 11:11 AM, Gerhard Wiesinger wrote:
>>> Hello,
>>>
>>> I'm having compile/link errors on
>>> 85f38553031b1a6e07f786c9ab0d403af7252b4f:
>>> LINK x86_64-softmmu/qemu-system-x86_64
>>> ../libhw64/virtio-pci.o: In function `virtio_scsi_exit_pci':
>>> /root/download/qemu/git/qemu/hw/virtio-pci.c:956: undefined reference to
>>> `virtio_scsi_exit'
>>> ../libhw64/virtio-pci.o: In function `virtio_scsi_init_pci':
>>> /root/download/qemu/git/qemu/hw/virtio-pci.c:939: undefined reference to
>>> `virtio_scsi_init'
>>> collect2: ld returned 1 exit status
>>>
>>> Clean compile.
>>>
>>> Any ideas?
>>
>> You have a stale configuration file. A 'make distclean' should help.
>
> Such errors indicate a dependency issue that should be fixed though.
> (Same error here. Rebuilding after rm -rf * worked.)
>
> When I change target-specific default configs it always seemed to work
> okay, is pci.mak different in any way? Or maybe some make target is
> lacking a dependency on the regenerated config files?
%/config-devices.mak: default-configs/%.mak
I think you could add default-configs/pci.mak to this stanza and it would have
regenerated here.
Regards,
Anthony Liguori
>
> Andreas
>
prev parent reply other threads:[~2012-02-24 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 17:11 [Qemu-devel] Compile/link errors Gerhard Wiesinger
2012-02-24 17:27 ` Anthony Liguori
2012-02-24 18:09 ` Andreas Färber
2012-02-24 18:24 ` Anthony Liguori [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=4F47D5E8.1040204@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=lists@wiesinger.com \
--cc=pbonzini@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).