Re: Dropping multilib [Re: Bug#1100544: glibc adds some conflicts letting gcc-14-cross ftbfs]
Hi Andrea,
On Sat, Mar 15, 2025 at 07:40:46PM +0100, Andrea Pappacoda wrote:
> As the maintainer of xbyak, could you please better explain what is going on
> here? It seems there's something missing in this thread (I'm only subscribed
> to debian-cross, I don't follow GCC bug reports).
>
> I added g++-multilib as a test-only dependency on Xbyak because it is needed
> to run its test suite, but I don't really know what multilib is and how I
> could drop/replace this dependency.
xbyak uses the -m32 and -m64 flags off gcc. I suggest that these should
cease working. Those flags are ambiguous in the sense that their meaning
depends on the underlying architecture. For xybak, we can understand
their meaning as it only works on x86 architectures. You may replace the
use of multilib toolchains with cross toolchains. Where you build depend
on gcc-multilib [amd64] to use gcc -m32, you'd then depend on
gcc-i686-linux-gnu [amd64] and use i686-linux-gnu-gcc. Where you build
depend on gcc-multilib [i386] to use gcc -m64, you'd then depend on
gcc-x86-64-linux-gnu [i386] and use x86_64-linux-gnu-gcc. In the case of
xbyak, this transformation may require upstream changes.
Note however, that I'm not sure we already have consensus on abandoning
multilib.
Helmut
Reply to: