[Xen-devel] Xen-4.1-testing fails to "make tools"

[misiu godfrey <misiu.godfrey@xxxxxxxxx>]

Hello Xen community,

This is my first time reporting a bug, so please let me know if I make
any faux-pas so that I may correct them in the future.

I checked out Xen-4.1-testing from the Mercurial repository on
Wednesday (4/25/12) and attempted to compile it with "make world" on a machine running a
recent install of Debian 6 (squeeze) and encountered an error

described in the following text (tail-end of stderr):

...
git clone git://xenbits.xensource.com/qemu-xen-4.1-testing.git ioemu-remote.tmp

Cloning into ioemu-remote.tmp...
remote: Counting objects: 80598, done.
remote: Compressing objects: 100% (22869/22869), done.

remote: Total 80598 (delta 60933), reused 76719 (delta 57621)
Receiving objects: 100% (80598/80598), 29.20 MiB | 6.08 MiB/s, done.

Resolving deltas: 100% (60933/60933), done.
+ [ a2d2123a7dfc4d116011d51f48df786a3b853537 ]

+ cd ioemu-remote.tmp
+ git branch -D dummy
+ :
+ git checkout -b dummy a2d2123a7dfc4d116011d51f48df786a3b853537
fatal: reference is not a tree: a2d2123a7dfc4d116011d51f48df786a3b853537
make[1]: *** [ioemu-dir-find] Error 128
make[1]: Leaving directory `/home/misiu/Xen/xen-4.1-testing.hg/tools'

make: *** [tools/ioemu-dir] Error 2

I later determined that the error could be isolated within "make tools"

Curiously, I was able to checkout and compile code from the same
repository the previous day (4/24/12) on the same machine without any
problems.  I have not managed to find any previous bug or
configuration problems that quite match up to this, but I did notice
that there was a single revision to the repository between these two

periods.  The revision in question can be found at
"xenbits.xen.org/hg/xen-4.1-testing.hg/rev/99517f769cc8" and

specifically refers to the area in question (QEMU git access).

I have now attempted to compile the current (4/25/12) release of
4.1-testing on two different machines, both running Debian 6, and

obtained the same results (shown above).

I hope I have provided enough information to address the situation and
if, to my embarrassment, it turns out to be an issue on my end I would

appreciate advice as to how to overcome the problem.

Thanks,
Misiu.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel