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. -- 🌐 Homepage https://johnscott.me 🪪 Contact info • as a vCard: https://johnscott.me/me/me.vcf • as an LDAP directory entry: ldap://johnscott.me/CN=John%20Scott,DC=johnscott,DC=me
signature.asc
Description: This is a digitally signed message part
smime.p7s
Description: S/MIME cryptographic signature
