It has finally been reproduced, and appears to be the fault of some unusual CFLAGS that get used in the builds made by the Ubuntu/Fedora packagers. Right now it is being tested to see what specific CFLAG is problematic.
It has finally been reproduced, and appears to be the fault of some unusual CFLAGS that get used in the builds made by the Ubuntu/Fedora packagers. Right now it is being tested to see what specific CFLAG is problematic.