pypy version 1.8+dfsg-2 failed to build on armhf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pypy (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
pypy version 1.8+dfsg-2 failed to build on armhf
Link to failed build: https:/
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 689 lines into the build log:
&& mem=$(($mem + 30708240)) || true; \
req_mem=1400; \
bits=32; \
[ $bits -ge 64 ] && req_mem=$(($req_mem * 2)) || true; \
if [ $(($req_mem * 1024)) -gt $mem ]; then \
echo "You don't have enough RAM to build PyPy."; \
echo "It's known to require >= $req_mem MiB on $bits bit archs."; \
exit 1; \
fi
You don't have enough RAM to build PyPy.
It's known to require >= 1400 MiB on 32 bit archs.
make[1]: *** [override_
make[1]: Leaving directory `/build/
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
*******
Build finished at 20120219-1918
FAILED [dpkg-buildpackage died]
Purging chroot-
Interesting that this is failing even before trying to build the package at Launchpad's builders. Need to check if it's counting swap, and if not, would probably make sense to improve the checking a bit to allow it at least to try to build it.