Re: support for multithread-safe libraries

[Paul Eggert]

Bruno Haible <address@hidden> writes:

> I propose to add a new module 'lock' to gnulib. It addresses these problems.
> It will be used in gettext 0.15.

Thanks very much for this.  I have one minor quibble: the name "lock".
That's a generic name, and "lock.h" is likely to collide with file
names already in use.  I just checked, and OpenBSD has a <sys/lock.h>;
I wouldn't be surprised if someone else (unwisely) grabbed <lock.h>.

How about if we use a name that is less likely to collide?  For
example, we use "lok", and the file names lok.h, lok.c, and lok.m4.
Or perhaps you can think of a better name.  ("gl-lock"? "gllock"? I
like puns, so I'd go with "lawk".  :-)


> dnl Solaris 7,8,9     posix       -lpthread   Y          Sol 7,8: 0.0; Sol 9: 
> OK
> dnl                   solaris     -lthread    Y          Sol 7,8: 0.0; Sol 9: 
> OK

I have access to a Solaris 8 sparc host.  Would it be worth my time to
see what the problem is on that host?  (I don't know what test-lock
is, though.)

That was an impressive array of hosts you tested on, by the way.  How
do you get access to such a wide variety?