From: Carsten Schiers <carsten@schiers.de>
To: "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Cc: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: xen-unstable 4.0-RC3 compile problem
Date: Tue, 16 Feb 2010 14:09:30 +0100 [thread overview]
Message-ID: <5706974.51266325770605.JavaMail.root@uhura> (raw)
Hi,
as usual, just when looking at 4.0-rc3-pre, next version is tagged :-)
I get a compile problem on Debian/Lenny (following some redefinition warnings):
pci.o: In function `pci_unplug_netifs': /usr/src/xen/xen-unstable.hg/tools/ioemu-dir/hw/pci.c:859: undefined reference to `test_pci_slot'
which I guess can relate to a recent change:
http://old.nabble.com/-qemu-xen-unstable--passthrough:-magic-ioport-protocol-no-longer-unplugs-passthrough-NICs-td27596616.html
Or am I wrong. 4.0-rc3-pre compiled just half an hor ago without any problems.
BR,
Carsten.
next reply other threads:[~2010-02-16 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 13:09 Carsten Schiers [this message]
2010-02-16 13:51 ` xen-unstable 4.0-RC3 compile problem Keir Fraser
2010-02-16 14:06 ` AW: " Carsten Schiers
2010-02-16 14:30 ` Ian Jackson
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=5706974.51266325770605.JavaMail.root@uhura \
--to=carsten@schiers.de \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).