FreeBSD 4.X will not support --enable-thread-safety in 7.5.  Let me
explain why.

In 7.4, if we didn't have a *_r function, and the non-*_r function was
not thread-safe, we called the non-*_r function with thread locks and
copied the value into the passed storage pointer.  I thought that was
OK, but several people pointed out that this was not safe if another
part of the program called the non-*_r function at the same time.  I
only understood the ramifications of that after 7.4 was released so I
didn't change the 7.4 code.

In 7.5, such locking/copying is gone, and if the function isn't
thread-safe, and there is no *_r function, we throw a configure error as
for threading.

FreeBSD 4.9 fails the getpwuid() test, and there is no getpwuid_r(). 
The documentation for getpwuid() is clear that it isn't thread-safe, so
I think the test is correct.

Basically, there is nothing we can do to fix this situation on FreeBSD
4.9 and probably other 4.X releases.

The good news is that the new configure tests for threading worked
perfectly and the system spit out a clear message explaining the
failure.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Sun, 25 Apr 2004 20:26:31 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
No threading option for FreeBSD 4.X in 7.5