From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6082] Fix the build for non-x86/ppc targets
Date: Thu, 18 Dec 2008 12:23:03 +0000 [thread overview]
Message-ID: <200812181223.04363.paul@codesourcery.com> (raw)
In-Reply-To: <E1LD87j-0002bd-CY@cvs.savannah.gnu.org>
On Thursday 18 December 2008, Anthony Liguori wrote:
> Revision: 6082
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6082
> Author: aliguori
> Date: 2008-12-18 01:56:22 +0000 (Thu, 18 Dec 2008)
>
> Log Message:
> -----------
> Fix the build for non-x86/ppc targets
>
> Since pci.c creates network devices, anything that links against pci.c
> (everything) has to link against all network devices. Since virtio-net
> also requires virtio, we might as well link every target against all of
> the virtio devices.
Is there any reason the virtio devices are x86/ppc specific?
I'd certainly hope that they'd work fine on any machine that supports PCI.
Paul
prev parent reply other threads:[~2008-12-18 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 1:56 [Qemu-devel] [6082] Fix the build for non-x86/ppc targets Anthony Liguori
2008-12-18 12:23 ` Paul Brook [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=200812181223.04363.paul@codesourcery.com \
--to=paul@codesourcery.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).