I guess that anyone who's been using Linux for long enough has already run into the message that some shared library (or plugin) can't be loaded because it uses static TLS.
KDE's Krita was one of the applications triggering that issue, when trying to load the G'Mic plugin if that was built using GCC's libgomp. I managed to avoid that by forcing it to use LLVM's libomp. And then discovered that a new enough Mesa (24.0.9 in my case) is very apt at triggering it all by itself, even in moderately simple apps like QMPlay2.
I have searched for but not found a "simple" test utility that can be used to search for the (e)glibc limits on static thread local storage. Is there such code, or how would one write it?
The error occurs when loading the triggering shared library, which means that there is probably no need to actually use the TLS variables, at least not in dedicated threads(?).
