After the glibc/filesystem/gcc upgrade this morning, I noticed that when linking a program, it now links it with /lib64/ld-linux-x86-64.so.2 rather than /lib/ld-linux-x86-64.so.2
Is this what is supposed to happen?
I'm not having any problems, I'm just checking that it is working properly.
listener: linux-vdso.so.1 (0x00007fff6e9ff000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f28a28b4000) /lib/ld-linux-x86-64.so.2 (0x00007f28a2c61000) listener2: linux-vdso.so.1 (0x00007fff94710000) libc.so.6 => /usr/lib/libc.so.6 (0x00007fbbede83000) /lib64/ld-linux-x86-64.so.2 (0x00007fbbee230000)
Last edited by rosslagerwall (2013-01-28 08:00:21)
Yes, I think so. See the commit log: https://projects.archlinux.org/svntogit … ages/glibc
Arch Linux is more than just GNU/Linux -- it's an adventure
I think this log is better: https://projects.archlinux.org/svntogit … ckages/gcc