Bug#854965: clang-4.0: Pulls 64-bit libs on i386 system

[Norbert Lange]

Hi,

there are a couple of libraries which pull in those depencies, ands
its probably a bad idea to use them at all. Those could/should be
moved to own packages, similar to the "multilib"s with gcc.
I proposed some new package layout in Bug #841923, but I am not sure
how this would work on the buildserver, every arch would generate its
static libraries in a arch=all package with a prefix and you could
pick libraries for any arch you like this way (even for baremetal
builds).
but then the control files would be different for each build and the
source archive...

I think the simplest and best fix for now would be to just kill the
depencies, eg (for AMD64):
dh_shlibdeps -Xlibclang_rt.asan-i686.so -Xlibclang_rt.asan-i386.so
(would need some fitting wildcards for the files)

You will have to install the fitting libc *anyway* for a 32bit build,
whether you use these libs or not, so I dont see a big problem with
skipping those deps.

Kind Regards, Norbert

2017-02-12 21:22 GMT+01:00 Sylvestre Ledru <sylvestre at debian.org>:
> severity 854965 normal
> thanks
>
> Le 12/02/2017 à 20:34, Robert Luberda a écrit :
>> Sylvestre Ledru pisze:
>>> Why do you consider that as serious?
>> The Debian Policy in section 3.5 says "Every package must specify the
>> dependency information about other packages that are required for the
>> first to work correctly."  It can be that the sentence is more about
>> depending on needed packages rather than about not depending on
>> unnecessary ones, but honestly I would still consider too wide
>> dependencies as a serious bug. However feel free lower the severity if
>> you disagree.
> yeah, I just did. This doesn't cause any severe issues.
>
>> Anyway in my opinion the 64-bit libraries are not needed for clang to
>> work correctly on i386. I can see that the libclang-common-dev package
>> started providing some x86_64 libs, and dpkg-shlibdeps added dependences
>> that were necessary for those libs; but I am really in doubt if clang
>> will ever use those libs in normal usage, so maybe there is some
>> packaging error somewhere? However if this was intentional for any
>> reason, it would be great if you could consider making the dev package
>> Multi-Arch:same instead to get rid of those strange 64-bit libs dependences.
> I think it was introduced in 3.9-5 to fix bug #841923. I guess 3.9 is
> also impacted
>
> Don't hesitate to propose a patch to implement Multi-Arch:same.
> I won't have the time to implement it soon.
>
> S
>