gcc-multilib version doesn't follow gcc-11-multilib in security

[Michał Fita]

I have a tool that requires `gcc-multilib` to be installed on jammy.

While I have `gcc-11-multilib` installed, an attempt to install `gcc-multilib` leads to suggestion some essential for me cross compilation gcc-11 packages are going to be removed, what doesn't make much sense.

This leaves me in some kind of a limbo, where I have everything I need to work in place (technically) but behaviour of not updated meta package leads to problems.

Could you, please, fix that?

[Michał Fita (michal.fita)]

I think problem lies elsewhere and till date haven't been solved even if `gcc-11-multilib` just works aside cross compilers installed.

https://groups.google.com/g/linux.debian.bugs.dist/c/S4eraIyuuzk

Looks like duplicate of: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1300211

Xilinx (Canonical's partner) requires `gcc-multilib` installed for their PetaLinux tools, while at the same time I need to cross-compile Debian packages for the ARM64 target on Xilinx chip. This is little bit awkward situation.

[Matthias Klose (doko)]

libc6-dev-i386 (dependency of gcc-multilib) installs files into /usr/include, which also is on the include path of the cross compilers.

[Michał Fita (michal.fita)]

But if platform dependent stuff lands directly in `/usr/include` that's flawed design of `libc6-dev-i386`.

This results in that I have to remove some packages and add different packages depending on what am I building...