newer glibc 2.19 and 2.20 is masked on armhf because they break and render the system unuseable.

The cause of this issue is probably just a wrong order in the ebuild and
simple to fix.
On a working machine (current/core) we have glibc-2.13 and such links :

/lib/ld-2.13.so
/lib/ld-linux-armhf.so.3 -> ld-linux.so.3
/lib/ld-linux.so.3 -> ld-2.13.so

after unmasking and emerging 2.19 we get this :

/lib/ld-2.13.so
/lib/ld-2.19.so
/lib/ld-linux-armhf.so.3 -> ld-2.19.so
/lib/ld-linux.so.3 -> ld-2.13.so

since /sbin/ln is linked against ld-linux.so.3 , i guess the ebuild fails here
in the same way it leaves the system with a defunctional /sbin/ln among others.

instant fix : correct links from outside chroot resp. with an alternative rootfs .

package-fix : change order of relinking/updating.