В Mon, 23 Aug 2010 11:01:14 -0700, Paul Eggert написа:
> On 08/23/10 10:28, John Calcote wrote:
>> What is the correct approach for this situation? Should I simply define
>> __USE_UNIX98 in my source code
>
> No, because that symbol is private to glibc. I wouldn't mess with it.
> Instead, use Aut
On 8/23/2010 12:01 PM, Paul Eggert wrote:
> On 08/23/10 10:28, John Calcote wrote:
>> What is the correct approach for this situation? Should I simply define
>> __USE_UNIX98 in my source code
> No, because that symbol is private to glibc. I wouldn't mess with it.
> Instead, use Autoconf's AC_USE_
On 08/23/10 10:28, John Calcote wrote:
> What is the correct approach for this situation? Should I simply define
> __USE_UNIX98 in my source code
No, because that symbol is private to glibc. I wouldn't mess with it.
Instead, use Autoconf's AC_USE_SYSTEM_EXTENSIONS.
__
On 08/23/2010 11:28 AM, John Calcote wrote:
Hi all,
I ran into an interesting issue today. Hoping some of you have some
insight for me. I needed to use a later addition to the pthreads spec -
pthread_mutexaddr_settype (in order to initialize a recursive mutex). To
use this function, you need t
Hi all,
I ran into an interesting issue today. Hoping some of you have some
insight for me. I needed to use a later addition to the pthreads spec -
pthread_mutexaddr_settype (in order to initialize a recursive mutex). To
use this function, you need to define __USE_UNIX98 before including
pthread.
