On 2025-03-15 14:25, Matthias Klose wrote: > This is exactly thing I am asking Helmut about. Then ok, I'll handle that > more strict. My first priority are the native packages, then the cross > packages in the archive. In the past I've seen unfortunately patches which > break either of these, and where claims were made, that these were tested, > which in the end, were not tested.
This time the change was done by Helmut, but in the past you also complained about my changes. Again I can't build glibc + cross-toolchain-base + gcc-X-cross for each small change. > > > > > This is now the another time that patches from Helmut for > > > > > out-of-the-archive > > > > > cross builds are breaking the in-archive cross compilers. > > > > > > > > You are completely mixing things. This has nothing to do with > > > > out-of-the-archive cross build. Those are conflicts that users can > > > > encounter when installing libc-dev biarch packages on a multiarch > > > > system. And as you say it well: Users are our priority! > > > > > > How many users are affected by this? If users are confused by multilib > > > packages, then let's remove them in trixie. No need to have them anymore > > > in > > > forky, I assume. People can use the cross compilers instead. > > > > I am all for removing the biarch packages, especially the ones built by > > c-t-b, I never understood their use case, and that will have prevented > > this bug to happen. But each time I talked about disabling multilib in > > gcc, you told me you don't want to diverge from upstream. Has your > > position changed since then? > > yes, once you have a solution to depend on foreign architectures, for both > release and ports architectures. Are you willing to work on this? No, I'm > not fine to drop support before there is a replacement. No I am not planning to work on that. That said, as a first step, this does not prevent removing multilib packages from the cross packages. For instance on an arm64 host, instead of installing gcc-x86-64-linux-gnu + gcc-multilib-x86-64-linux-gnu to use x86_64-linux-gnu-gcc with -m32, one can just install gcc-i686-linux-gnu and call i686-linux-gnu-gcc. And there is a nobiarch build profile that can be used. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
