On Mon, 1 Sep 2003, Peter Eisentraut wrote:
> Greg Stark writes:
>
> > Um. I don't think that's true. I mean, in theory it's true, but in practice
> > why would an OS have some *_r but have only non-thread-safe versions of
> > others?
>
> The question is whether configure can reliably identify whether various
> *_r functions exist. I think it can't. For example, they could be in a
> separate library that we don't know about.
'K, but isn't that just a matter of adding an extra test when such
'extra libraries' are identified? I've seen it before, in order
configures, where it tests for the same function in a couple of different
libraries ...