Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25
On 2017-11-21 00:15, Mikulas Patocka wrote:
>
>
> On Mon, 20 Nov 2017, Aurelien Jarno wrote:
>
> > On 2017-11-20 21:58, Mikulas Patocka wrote:
> > >
> > >
> > > On Mon, 20 Nov 2017, Samuel Thibault wrote:
> > >
> > > > Mikulas Patocka, on lun. 20 nov. 2017 19:13:31 +0100, wrote:
> > > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which provide
> > > > > x86-64 libc in /lib64/). This package is not technically needed (because
> > > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but it is
> > > > > installed nonetheless because of some dependencies.
> > > >
> > > > The issue of libc6-amd64:i386 conflicting with libc6:amd64 is not new, I
> > > > tried to do it in the past, just to see, with the same kind of effect as
> > > > you had.
> > > >
> > > > The question is rather how that got pulled at all. What package thinks
> > > > it's a good idea to pull libc6-amd64? Apart from libc64* packages
> > > > (which should normally not get pulled either), I can see uc-echo which
> > > > should rather use foreign dependencies, and :i386 multilib packages
> > > > which don't really make sense to install either.
> > > >
> > > > I don't remember whether it was tried to make libc6-amd64:i386 conflict
> > > > with libc6:amd64 (and vice-versa for i386) to make sure that this
> > > > doesn't happen by misfortune?
> > > >
> > > > Samuel
> > >
> > > libc6-amd64 is pulled by lib64asan0, lib64asan1, lib64asan2, lib64asan3,
> > > lib64asan4, lib64atomic1, lib64cilkrts5, lib64gcc1, lib64gomp1, lib64itm1,
> > > lib64quadmath0, lib64stdc++6, lib64ubsan0, libc6-dev-amd64.
> > >
> > > If you install gcc-7-multilib for non-default architecture (i386 or x32),
> > > it will inevitably pull libc6-amd64.
> >
> > What's the point of doing that, as opposed for example building with
> > -m32 or mx32?
>
> The native x32 gcc binary is about 10% faster than the amd64 binary.
In that case you can install only gcc-7:x32 instead of gcc-7-multilib:x32,
which won't pull libc6-amd64:x32.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: