Re: -rpath and policy?
Colin Watson <firstname.lastname@example.org> writes:
> On Tue, Jun 15, 2004 at 09:13:46AM +0200, Goswin von Brederlow wrote:
>> Colin Watson <email@example.com> writes:
>> > On Mon, Jun 14, 2004 at 03:50:46PM +0200, Goswin von Brederlow wrote:
>> >> Where should compatibility links point to?
>> >> i386:~% ldd =echo
>> >> linux-gate.so.1 => (0x00000000)
>> >> libc.so.6 => /lib/libc.so.6 (0x55577000)
>> >> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x55555000)
>> >> amd64:~% ldd =echo
>> >> libc.so.6 => /lib/libc.so.6 (0x0000002a9566b000)
>> >> /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x0000002a95556000)
>> >> Which of the two libc6.so.6 shoud it point to?
>> > Whatever was previously in the location of the symlink.
>> Which one? The 32bit one or the 64bit one? Notice how they both are
>> exactly the same location and name.
> ... on different architectures, thus in different .debs. I see no
> problem here.
The mutliarch moves the libs around so they don't exist in the same
place for the purpose of installing both archs packages in parallel.
That means you can have a 32bit bash and a 64bit ls and both 32 bit
and 64bit libc6 for them.
Good news though. When multilib takes hold the lib64 -> lib links
could be removed, then 32bit and 64bit libs would be in different
places again and both could be linked to the multiarch dirs. Just
means all of debian has to be ported to multiarch (or lib64 dirs) so
broken software can be fixed with links.