Out of curiousity, how does this interact with the dynamic TLS library feature? It looks like it doesn't and just hard codes one path, but, presumably, the path returned by this feature isn't necessarily the one that's being used by the TLS library being selected at run-time. In fact, isn't this path going to be completely ignored on some TLS libraries? These should at least be documented if they can't be fixed.

Good point. I'll convert your comment to an issue to make sure we don't forget it!