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


Re: [Xen-devel] build of xen-unstable(cs:19963 and 19974) failed for i38

To: mike xiao <mike.xiao@xxxxxxxxxx>
Subject: Re: [Xen-devel] build of xen-unstable(cs:19963 and 19974) failed for i386/x86_64
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 4 Aug 2009 14:12:36 +0100
Cc: "Maturi, Srinivas" <srinivas.maturi@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 04 Aug 2009 06:13:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A68284C.4010603@xxxxxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <4A68284C.4010603@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
mike xiao writes ("[Xen-devel] build of xen-unstable(cs:19963 and 19974) failed 
for i386/x86_64"):
> Build infomation:
>   build of xen-unstable(cs:19963 and 19974) failed for 
> i386/x86_64,details as below:
> xenbits.xensource.com[0:]: errno=No route to host
> fatal: unable to connect a socket (No route to host)

I think this means that either:
 (a) there was a temporary network problem
 (b) your firewall is preventing access to the xenbits git repository.

If the problem persists, the answer is (b).  There are two possible
fixes: 1. fix your firewall to allow git through; 2. use the tree via
http (slower and less efficient).

To do 2, change the definition of QEMU_REMOTE to
by editing Config.mk or setting it in .config in your xen-unstable tree.


Xen-devel mailing list

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