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
Invalid according to whom?
The cost to Ubuntu is one symlink to be compatible with many more
binaries. The pure64 systems are so by design obviously, so no lib64 is
quite valid in their eyes.
** Changed in: glibc (Ubuntu)
Status: Invalid => New
--
You received this bug notification becau
$ ldd hello
linux-vdso.so.1 => (0x7fffb4c93000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0869264000)
/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
(0x7f086964b000)
this is an invalid dynamic linker name. you should complain with the
people
Any binary compiled on a pure64 system, those systems do not have a
/lib64 directory. Attaching a "hello world" for your testing.
** Attachment added: "Hello world binary"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1318598/+attachment/4137964/+files/hello
--
You received this bug n
The canonical location for the 64-bit linker is in /lib64, not /lib ...
Which third party applications expect otherwise? No compiler should be
producing such broken output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
