Re: Bug#277972: glibc: Please change the remaining instances of 'lib64' to 'lib' on amd64
On Sun, Oct 24, 2004 at 10:18:15PM +0200, Andreas Jochens wrote:
> This patch is harmless with respect to any LSB requirement.
> The name of the dynamic loader, which is coded into every binary
> can only be changed in the gcc package. This patch does not change
I don't know what you all changed in the gcc-3.4 archive. But
this is what I now get with something I just compiled:
libc.so.6 => /lib/libc.so.6 (0x0000002a9566d000)
/lib/ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x0000002a95556000)
While with the pure64 archive with either gcc-3.3 of 3.4 it's
still pointing to /lib64/ld-linux-x86-64.so.2
> Furthermore, there is no LSB requirement which requires the
> dynamic loader to be installed in '/lib64' or to be accessible
> as '/lib64/ld-linux-x86-64.so.2'.
> The LSB requires that the dynamic loader is accessible through
> '/lib64/ld-lsb-x86-64.so.2' (note the 'lsb' instead of 'linux' in the
You seem to be right on that:
| Program Interpreter/Dynamic Linker
| The LSB specifies the Program Interpreter to be /lib64/ld-lsb-x86-64.so.2.
> middle). This is being taken care of by the 'lsb' package
> which installs a symlink '/lib64/ld-lsb-x86-64.so.2'
> which points to '/lib/ld-linux-x86-64-so.2' (actually, the current
Should probably atleast be a .
> version of the 'lsb' package still has a bug which lets the symlink
> point to '/lib/ld-linux.so.2' instead).
I just notices that same bug too.
> The LSB does not specify anything else regarding the location of
> the dynamic loader besides that is must be accessible through
Well, it seems that atleast it doesn't change anything with
compliance to the LSB. But I still think it's wrong.
Either glibc or gcc, whichever places that hardcoded path,
should point to either /lib64/ld-lsb-x86-64.so.2 or
/lib64/ld-linux-x86-64.so.2. And since the LSB says it should be
/lib64/ld-lsb-x86-64.so.2 I would even say it should be changed
Anything else is going to cause problems running our binaries on
an other distribution. We should also make sure that programs
build on an other distro can be run on debian so I think we also
need to have a "/lib64/ld-linux-x86-64.so.2" provided in some