Bug#830913: debian-policy: Allow amd64 systems without /lib64
Javier Serrano Polo <javier@jasp.net> writes:
> Some amd64 systems do not have /lib64, although they can run programs
> with the interpreter set to /lib64/ld-linux-x86-64.so.2 . It would be
> nice if Debian could allow such systems. In section 9.1.1, where it
> says:
> The execution time linker/loader, ld*, must still be made
> available in the existing location under /lib or /lib64
> "must" should be "should".
You reported the above bug six years ago, and it looks like it never
received a reply. I'm sorry about that!
I'm confused by this bug report, though. What does "some amd64 systems"
mean in this context? It looks to me like the amd64 libc6 package
provides /lib64/ld-linux-x86-64.so.2, so a Debian amd64 system would
satisfy this. Is there some alternate libc6 package available in Debian
that does things differently? Or are you thinking of some sort of
container or other type of restricted system?
Also, in this case, how does this work? Is the path somehow remapped at
the kernel level? (If so, I'm wondering if that would qualify as "made
available" for the purposes of Policy anyway.)
--
Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>
Reply to: