Invalid according to the x86_64 Linux ELF spec. There can be only one
canonical location for the dynamic linker, and people building a
compiler that doesn't respect that are building a broken compiler.
Ubuntu and Debian are "pure64" are well, in the sense that we put our
libraries in /lib, but we still put the linker in /lib64 because that's
where it's meant to be. Period.
Whatever this pure64 toolchain is, it's wrong, plain and simple. We
can't cater to any time someone decides to put the linker in the wrong
path, so I don't intend to cater to one special case either. That way
lies madness.
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318598
Title:
64-bit linker symlink missing, causing third-party binaries not to run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1318598/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
