[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: support for multithread-safe libraries
From: |
Bruno Haible |
Subject: |
Re: support for multithread-safe libraries |
Date: |
Mon, 18 Jul 2005 22:02:33 +0200 |
User-agent: |
KMail/1.5 |
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 on Solaris, OSF/1, HP-UX, the use of -D_REENTRANT has the effect of
defining 'errno' differently. Does this mean that exported library functions
that set errno, built with -D_REENTRANT, will not work with a program that
has been built without -D_REENTRANT ?
All I know is that glibc does not have this problem. But what exactly is
the extent of the problem on these three Unices?
Bruno
- Re: support for multithread-safe libraries, (continued)
Re: support for multithread-safe libraries, Oskar Liljeblad, 2005/07/15
Re: support for multithread-safe libraries, Albert Chin, 2005/07/19
Re: support for multithread-safe libraries, Albert Chin, 2005/07/19