http://bugs.winehq.org/show_bug.cgi?id=59734 --- Comment #6 from Joachim <joachim.ionoff@gmail.com> --- Ok, I found the root cause. It is on lib32-nettle build package rules. Building the nettle has changed on 4.0 as per the announce on gnu.org (https://lists.gnu.org/archive/html/info-gnu/2026-02/msg00002.html): * The unusual configure options --with-lib-path and --with-include-path has been deleted. Use CFLAGS and LDFLAGS instead. This implies that Nettle's configure script no longer attempts to add rpath-related linker flags automagically; if any are needed, they must be passed in LDFLAGS. * The logic to sometimes change the default libdir has been deleted. Previously, configure tried to be helpful and change the default, e.g., to ${exec_prefix}/lib32 when you build 32-bit libraries on a system where ${exec_prefix}/lib is for 64-bit libraries. If you relied on this behavior, you now have to use the --libdir configure option. Something mismatched with GMP lib used. I suspect it was not the 32-bit library of GMP. Mostly, I added those compile flags and it is now successfully login. export CPPFLAGS+=" -m32 -I/usr/lib32/gmp" export LDFLAGS+=" -m32 -L/usr/lib32 -lgmp" Sorry for wasting your time. I'll open an issue on the Arch Linux packages with my working PKGBUILD. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.