From: mike xiao <mike.xiao@oracle.com>
To: xen-devel@lists.xensource.com, srinivas.maturi@oracle.com
Subject: build of xen-unstable(cs:19981) failed for i386/x86_64
Date: Fri, 24 Jul 2009 17:43:43 +0800 [thread overview]
Message-ID: <4A69824F.5020600@oracle.com> (raw)
Build infomation:
build of xen-unstable(cs:19963 and 19974) failed for
i386/x86_64,details as below:
make[1]: Entering directory `/builddir/build/BUILD/xen-unstable/tools'
set -ex; \
if test -d git://xenbits.xensource.com/qemu-xen-unstable.git; then \
rm -f ioemu-dir; \
ln -sf git://xenbits.xensource.com/qemu-xen-unstable.git ioemu-dir; \
else \
if [ ! -d ioemu-remote ]; then \
rm -rf ioemu-remote ioemu-remote.tmp; \
mkdir ioemu-remote.tmp; rmdir ioemu-remote.tmp; \
git clone git://xenbits.xensource.com/qemu-xen-unstable.git ioemu-remote.tmp; \
if [ "5cc34ea27f1cbd1a0560cfca91fb89ccd6d5726f" ]; then \
cd ioemu-remote.tmp; \
git branch -D dummy >/dev/null 2>&1 ||:; \
git checkout -b dummy 5cc34ea27f1cbd1a0560cfca91fb89ccd6d5726f; \
cd ..; \
fi; \
mv ioemu-remote.tmp ioemu-remote; \
fi; \
rm -f ioemu-dir; \
ln -sf ioemu-remote ioemu-dir; \
fi
+ test -d git://xenbits.xensource.com/qemu-xen-unstable.git
+ '[' '!' -d ioemu-remote ']'
+ rm -rf ioemu-remote ioemu-remote.tmp
+ mkdir ioemu-remote.tmp
+ rmdir ioemu-remote.tmp
+ git clone git://xenbits.xensource.com/qemu-xen-unstable.git ioemu-remote.tmp
Initialize ioemu-remote.tmp/.git
xenbits.xensource.com[0: 70.42.241.107]: errno=No route to host
fatal: unable to connect a socket (No route to host)
Initialized empty Git repository in /builddir/build/BUILD/xen-unstable/tools/ioemu-remote.tmp/.git/
make[1]: *** [ioemu-dir-find] Error 128
make[1]: Leaving directory `/builddir/build/BUILD/xen-unstable/tools'
make: *** [tools/ioemu-dir] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.29742 (%build)
reply other threads:[~2009-07-24 9:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A69824F.5020600@oracle.com \
--to=mike.xiao@oracle.com \
--cc=srinivas.maturi@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.