All I can do is give you a couple of Github ticket links where users of my libraries stumbled over the issue (and with different symptoms): - https://github.co

All I can do is give you a couple of Github ticket links where users of my libraries stumbled over the issue (and with different symptoms): - https://github.com/floooh/sokol/issues/376 https://github.com/floooh/sokol/issues/376 - https://github.com/floooh/sokol/issues/404 https://github.com/floooh/sokol/issues/404 - https://github.com/floooh/cimgui-sokol-starterkit/issues/6 https://github.com/floooh/cimgui-sokol-starterkit/issues/6 We then added a dummy call to a no-op pthread function, so that users at least get a pthread-related linker error and can figure out that they need the -pthread/-lpthread options instead of running into random runtime problems: - https://github.com/floooh/sokol/pull/456 https://github.com/floooh/sokol/pull/456 Also, on my Ubuntu laptop this problem didn't happen, that's why I didn't catch it during development, it seems to be specific to some distros or personal config changes. The affected code bases don't use threading and didn't link pthread before (neither statically nor dynamically).