Re: support for multithread-safe libraries

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 >

Re: support for multithread-safe libraries

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

adding once-only initialization to lock module

Hi, Libraries that need to protect shared datastructures with locks also often need once-only initializations. And conversely, all programs that need thread-safe once-only initialization also need locking. So I've added support for once-only execution (à la pthread_once) to lock.h and lock.c. Br

Re: support for multithread-safe libraries

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

Re: [bug-gnulib] Re: quoting in gnulib

[EMAIL PROTECTED] (Bob Proulx) writes that : > looks fine to me too on my stock Debian GNU/Linux 3.1 sarge system > running Firefox 1.0.4. (I am saying this only so that readers of the > archive later won't think this is intr

Re: check_version

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> having a AC_DEFINE seem somewhat hackish. > > No, why is this odd? Here's what I use in gettext to avoid collisions of > the "lock in libintl" with "lock outside libintl". Perhaps it is OK. I had another reason for disliking th

Re: check_version

Simon Josefsson wrote: > having a AC_DEFINE seem somewhat hackish. No, why is this odd? Here's what I use in gettext to avoid collisions of the "lock in libintl" with "lock outside libintl". dnl Rename some macros and functions used for locking. AH_BOTTOM([ #define glthread_lock_init libi

Re: [bug-gnulib] Re: support for multithread-safe libraries

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

Re: getline

Paul Eggert <[EMAIL PROTECTED]> writes: > Simon Josefsson <[EMAIL PROTECTED]> writes: > >> 5. I have no idea whether using flockfile/funlockfile is appropriate. > > I'd say it's appropriate, but only if flockfile/funlockfile exist. > They don't exist on all platforms. POSIX says they're optional;