Arch Linux

/lib has been made a symlink to /usr/lib as temporary (?) compatibility solution, but GCC (or ld) still link new binaries against /lib/ld-linux-x86-64.so.2 (with absolute path) instead of /usr/lib/ld-linux-x86-64.so.2.

Newly compiled packages and user-compiled apps should be linked to /usr/lib/ld-linux-x86-64.so.2 to further advance with /lib -> /usr/lib move, newly compiled packages shouldn't depend on old filesystem layout.

This shouldn't affect portability of user-compiled binaries to other linux distributions, since most of them don't have /lib/ld-linux-x86-64.so.2 anyway. They have 32bit version of ld-linux in this directory and 64bit version in /lib64 so old binaries didn't work in other distributions anyway, unless symlink was created in /lib.

The only compatibility issues might arise when moving user-compiled programs to not-updated version of Arch Linux where /usr/lib/ld-linux-x86-64.so.2 doesn't exist yet, but that is good, because (1) it would force users to update outdated systems to fix possible security issues in old packages (2) and can be easily fixed on outdated system by creating a symlink. And because partial updates are officially unsupported, user's shouldn't have new packages installed along with old glibc, so no problem here.

I myself consider this a bug, which should be fixed (in GCC/ld/binutils, whereever this path is hardcoded), then newly compiled packes would get fixed too and eventually everything would be compiled against the right library. Then Arch Linux could really say '/lib' was moved to '/usr/lib'.