On Tue, 2009-03-17 at 11:52 +0100, Goswin von Brederlow wrote:
> Ian Campbell <i...@hellion.org.uk> writes:
>
> > On Mon, 2009-03-16 at 14:36 +0100, Goswin von Brederlow wrote:
> >>
> >> Note that libc6 and libc6-i386/amd64 will neccessarily always conflict
> >> due to the dynamic linker
> >
> > Really? I thought the i386 dynamic linker was /lib/ld-linux.so.2 and the
> > 64 bit one was /lib/ld-linux-x86-64.so.2.
> >
> > Ian.
>
> Libc6 on i386 and libc6-i386 both have /lib/ld-linux.so.2.
>
> Libc6 on amd64 has lib64 -> lib and /lib/ld-linux-x86-64.so.2 and
> libc6-amd64 has /lib64/ld-linux-x86-64.so.2.
Sorry I misread what you said and thought you were saying that the
arch:i386 libc6 and arch:amd64 libc6 packages would conflict in a
multiarch world but reading closer I see you were talking about the
existing biarch libc6-{i386,amd64} packages. Fair enough.
Ian.
--
Ian Campbell
The Roman Rule:
The one who says it cannot be done should never interrupt the
one who is doing it.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
