[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-devel] build of xen-unstable(cs:19963 and 19974) failed for i386/x86_64
/me bets this isn't the last time this question will need
to be answered.
Since my rant yesterday was (perhaps justifiably) ignored *,
could you please at least put the alternate QEMU_REMOTE
in Config.mk as a comment and add a line or two to
the main README (with something like "if git repeatedly
> -----Original Message-----
> From: Ian Jackson [mailto:Ian.Jackson@xxxxxxxxxxxxx]
> Sent: Tuesday, August 04, 2009 7:13 AM
> To: Mike Xiao
> Cc: Srinivas Maturi; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] build of xen-unstable(cs:19963 and 19974)
> failed for i386/x86_64
> 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: 188.8.131.52]: 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
Xen-devel mailing list