Albert Chin wrote:
> So, according to your test, #pragma weak supports weak symbols on
> Solaris and IRIX 6.5.
Yes, I confirm this.
> However, in the case of pthread mutex'es, you
> should really test for working stubs in libc:
> http://lists.freedesktop.org/archives/cairo/2005-July/004465.html
On Thu, Jul 14, 2005 at 04:10:14PM +0200, Bruno Haible wrote:
> I propose to add a new module 'lock' to gnulib. It addresses these problems.
> It will be used in gettext 0.15.
I looked through m4/lock.m4 to determine how you identify weak symbol
support on a system:
gl_have_weak=no
AC_TRY_
On Thu, Jul 14, 2005 at 04:10:14PM +0200, Bruno Haible wrote:
> dnl Survey of platforms:
> dnl
> dnl Platform Available CompilerSupports test-lock
> dnl flavoursoption weak result
> dnl --- - - -
On Mon, 2005-07-18 at 21:41 +0200, Bruno Haible wrote:
> Oskar Liljeblad wrote:
> > http://autoconf-archive.cryp.to/acx_pthread.html uses a set of
> > tests for pthread support.
>
> Thanks for the info. I'll use this as a reference when there's need to.
>
> > Some notes from it:
>
> > -pthread
>
Oskar Liljeblad wrote:
> http://autoconf-archive.cryp.to/acx_pthread.html uses a set of
> tests for pthread support.
Thanks for the info. I'll use this as a reference when there's need to.
> Some notes from it:
>
> -lpthreads
> AIX (must check this before -lpthread)
> (no flags)
> in case thr
Oskar Liljeblad wrote:
> http://autoconf-archive.cryp.to/acx_pthread.html
That macro also contains this:
case "${host_cpu}-${host_os}" in
*-aix* | *-freebsd* | *-darwin*) flag="-D_THREAD_SAFE";;
*solaris* | *-osf* | *-hpux*) flag="-D_REENTRANT";;
esac
But
Paul Eggert wrote:
> Here's a little bit more evidence. I just checked Debian stable, and
> it has an /usr/include/lock.h, installed by an AFS development
> package. See:
>
> http://packages.debian.org/cgi-bin/search_contents.pl?searchmode=filelist&word=arla-dev&version=stable&arch=i386
This pac
Bruno Haible <[EMAIL PROTECTED]> writes:
> So I still think the name "lock" is fine.
Here's a little bit more evidence. I just checked Debian stable, and
it has an /usr/include/lock.h, installed by an AFS development
package. See:
http://packages.debian.org/cgi-bin/search_contents.pl?searchmod
On Thursday, July 14, 2005 at 16:14, Bruno Haible wrote:
> dnl Survey of platforms:
> dnl
> dnl Platform Available CompilerSupports test-lock
> dnl flavoursoption weak result
> dnl --- - - -
> dn
Paul Eggert wrote:
> The word "lock" is good, but (unfortunately) lots of things are
> locked, and there are different forms of locks. Files can be locked
> with flock, for example. "lock.h" could refer to any of these things.
"flock" and "lockf" are the common names of that.
> > and resembles
Bruno Haible <[EMAIL PROTECTED]> writes:
> "lock.h" has the big benefit that it describes what it is
The word "lock" is good, but (unfortunately) lots of things are
locked, and there are different forms of locks. Files can be locked
with flock, for example. "lock.h" could refer to any of these
Paul Eggert wrote:
> 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 ;
> I wouldn't be surprised if someone else (unwisely) grabbed .
FreeBSD is going away from , they renamed
On Thu, Jul 14, 2005 at 11:34:51AM -0700, Paul Eggert wrote:
> 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 "la
Bruno Haible <[EMAIL PROTECTED]> 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
name
14 matches
Mail list logo
