@bsek I imagine some optimization (probably in clang) uses a function from stdc, causing the shared library to be pulled in

if so, it has to be gcc - but not important. Just wondered since I have not experienced this problem.

possible, but the last time I had to fix it was due to clang converting a recognized pattern into memset or smilar - an as far as I recal the "fix" was to tell it to not use builtins