The last published arm stages (even autobuilds) are from 2016, and still contain gcc-4. This gcc does not build recent glibc releases (>=2.26) anymore.
Releases available at https://files.emjay-embedded.co.uk/unofficial-gentoo/arm-stages/ contain gcc-6.4.0-r1 currently. RESO:FIXED
The armv7a_hardfp stage3 (dated 2016-11-29) contains a populated ./tmp/stage1root. This: 1) wastes disk space (when uncompressed); 2) prevents using the stage3 tarball as a catalyst seed stage to build a newer stage1, due to conflicts with the old version of sandbox and stable versions in a current portage tree.
(In reply to Daniel Cordero from comment #2) > The armv7a_hardfp stage3 (dated 2016-11-29) contains a populated > ./tmp/stage1root. > > This: > 1) wastes disk space (when uncompressed); > 2) prevents using the stage3 tarball as a catalyst seed stage to build a > newer stage1, due to conflicts with the old version of sandbox and stable > versions in a current portage tree. 99% sure this has been fixed on one of the many updates to catalyst, and /tmp is completely cleaned out. It shouldn't even reach the stage 2 let alone the 3!!
*** Bug 654994 has been marked as a duplicate of this bug. ***
we have newer at distfiles.g.o as I see this
