This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] stubdom questions

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] stubdom questions
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 09 Nov 2010 10:44:23 +0000
Delivery-date: Tue, 09 Nov 2010 02:44:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Is it intentional that
- large parts of stubdom build with -j1 only irrespective of the original
make invocation?
- all imported packages are out of date?
- pciutils is being built without 64-bit support (visible via warnings issued
from the qemu build)?
- the build produces dozens of compiler warnings quite a few of which
don't look benign at all?
- can't be built with a read-only and/or symlinked source tree?

Also, what's the point of the install-stubdom dependency on
install-tools? Shouldn't the individual components' builds be
independent of one another?

Thanks, Jan

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>