On Mon, 15 Jul 2024 15:28:40 +0000 John Scott <jsc...@posteo.net> wrote: > Andreas wrote: > > the sse4.1 requirement seems to have been added as a workaround for > > some other problem specifically on the i386 architecture, but I > > will investigate and try to provide a fix. > > Let me know if you want a hand or for me to look over anything: I > know a thing or two about GCC, in particular with building cross > toolchains with it. Also note that since the build flags are injected > in both Bookworm and Trixie/Sid, you'll probably need to work on two > fixes. > > The alleged GCC bug may have been fixed in newer GCC 13 uploads. If > that's the case, I can help you bisect to set an appropriate build > dependency on a fixed version. If no fixed GCC 13 appears to be > packaged, the GCC maintainers could probably apply a patch to > Bookworm and Trixie/Sid, and then a tight build dependency would save > the day. > > I'll leave you to doing what you've got to do, but I'm here. > --
You might have seen the thread I started on debian-devel [1], where they think that this is really a problem in filezilla which should be fixed. From the minor tests I have done, filezilla (without the msse4.1 patch applied) builds fine on gcc-14 on i386 (and all other arches), which however isn't even in unstable yet. I have of course also tested also building with the gcc in unstable (13) on i386 without the patch, and there filezilla doesn't build. The fix in gcc-14 seems to be this: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=9a19fa8b616f83474c35cc5b34a3865073ced829 But I of course understand that it most probably is a big investment to get something like this into stable. (oh, why did I adopt this package... ;) /Andreas 1: https://lists.debian.org/debian-devel/2024/07/msg00240.html
