@DataDrake Thanks for the suggestion. I've looked into this a bit more and found the same issue across many linux distros. My current conlusion is that it is something weird that tcc does, and modern changes to system libs have created this message.
However! The binaries build by tcc actually run, even though they report this runtime error. So, in a lavish display of ersatz engineering, I've created a tcc script that calls the real tcc and greps away those specific error lines. My job here is done!
