Your message dated Mon, 5 Mar 2018 21:04:37 +0100
with message-id <20180305200437.ga7...@aurel32.net>
and subject line Re: Bug#890801: libc6-i386 conflicts with libc6-amd64:i386
has caused the Debian Bug report #890801,
regarding libc6-i386 conflicts with libc6-amd64:i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
890801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-i386
Version: 2.26-6
Severity: important
Dear Maintainer,
I tried cross compile 32-bit Mesa on 64-bit Debian (amd64), and I had to
install these packages in order to do it:
llvm-5.0-dev:i386 libclang-5.0-dev:i386 gcc-multilib g++-multilib
Unfortunately it failed, and I managed to narrow it down to the conflict
between libc6-i386 conflicts and libc6-amd64:i386:
sudo apt-get install libc6-amd64:i386 libc6-i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-amd64:i386 : Conflicts: libc6-i386 but 2.26-6 is to be installed
libc6-i386 : Conflicts: libc6-amd64:i386 but 2.26-6 is to be installed
E: Unable to correct problems, you have held broken packages.
How can this be resolved?
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libc6-i386 depends on:
ii libc6 2.26-6
libc6-i386 recommends no packages.
libc6-i386 suggests no packages.
--- End Message ---
--- Begin Message ---
On 2018-02-19 10:18, Aurelien Jarno wrote:
> On 2018-02-18 19:17, Hillel Lubman wrote:
> > Package: libc6-i386
> > Version: 2.26-6
> > Severity: important
> >
> > Dear Maintainer,
> >
> > I tried cross compile 32-bit Mesa on 64-bit Debian (amd64), and I had to
> > install these packages in order to do it:
> >
> > llvm-5.0-dev:i386 libclang-5.0-dev:i386 gcc-multilib g++-multilib
> >
> > Unfortunately it failed, and I managed to narrow it down to the conflict
> > between libc6-i386 conflicts and libc6-amd64:i386:
>
> You can install only one set of multilib package at the same time,
> otherwise you end up with files conflict. In your case llvm-5.0-dev:i386
> requires the :i386 version of the multilib set, while gcc-multilib
> requires the :amd64 version of it.
>
> > sudo apt-get install libc6-amd64:i386 libc6-i386
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> > libc6-amd64:i386 : Conflicts: libc6-i386 but 2.26-6 is to be installed
> > libc6-i386 : Conflicts: libc6-amd64:i386 but 2.26-6 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> >
> > How can this be resolved?
>
> If you want to install llvm for i386 you also need to install gcc for
> i386. The other option is to not install gcc-multilib and g++-multilib.
>
> If that solution is not acceptable for you, here are the few other
> alternatives I can think of:
> - report a bug against llvm to split libclang-common-5.0-dev into two
> parts, one providing the native support, the other one the multilib
> support, just like it is done in GCC.
> - report a bug against llvm to support a multiarch alternative to the
> 64-bit libraries. That means for example changing the lib64gcc1:i386
> dependency into lib64gcc1:i386 | libgcc1:amd64. This might require
> code change to look into both multiarch and multilib paths.
> - report a bug against gcc to support a multiarch alternative to the
> 32-bit libraries.
> - report a bug against gcc-7-cross to add an i386 cross-compiler on
> amd64.
>
> There is nothing we can do on the glibc side.
As explain, we can't do anything from the glibc side. I am therefore
closing the bug.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
