Debian buildds writes ("failed armhf build of xen 4.8.0~rc3-1"):
> * Source package: xen
> * Version: 4.8.0~rc3-1
> * Architecture: armhf
> * State: failed
> * Suite: sid
> * Builder: hartmann.debian.org
> * Build log:
> https://buildd.debian.org/status/fetch.php?pkg=xen&arch=armhf&ver=4.8.0%7Erc3-1&stamp=1478544996&file=log
Debian buildds writes ("failed i386 build of xen 4.8.0~rc3-1"):
> * Source package: xen
> * Version: 4.8.0~rc3-1
> * Architecture: i386
> * State: failed
> * Suite: sid
> * Builder: x86-grnet-01.debian.org
> * Build log:
> https://buildd.debian.org/status/fetch.php?pkg=xen&arch=i386&ver=4.8.0%7Erc3-1&stamp=1478544915&file=log
These builds failed because they were done with binutils
2.27.51.20161105-1. That version had a severe bug that causes ld to
spin on the cpu (on amd64 and other architectures, apparently).
I uploaded xen 4.8.0~rc3-1 to sid after I observed that my amd64 sid
chroot had obtained 2.27.51.20161105-2 which has the fix. 4.8.0~rc3-1
has no code changes compared to 4.8.0~rc3-0exp2 which built on all
applicable architectures in experimental.
I see from
https://buildd.debian.org/status/package.php?p=binutils&suite=sid
that the fixed version of binutils is showing as "Installed" for armhf
and i386.
Have I done something wrong ? Do the buildd chroots need to be
updated ?
FYI, this is blocking the xen 4.8 transition. (CCing the transition
bug.)
Thanks,
Ian.
