On Thu, Feb 17, 2000 at 11:29:57AM -0500, Daniel Eischen wrote:
>
> How about we remove the #if defined()s for:
>
> _POSIX_THREAD_PROCESS_SHARED
> _POSIX_THREAD_PRIO_PROTECT
> _POSIX_THREAD_PRIO_INHERIT
> _POSIX_THREAD_PRIORITY_SCHEDULING
>
> from our ?
Yes, it looks like use of the la
On Thu, 17 Feb 2000, Daniel Eischen wrote:
> How about we remove the #if defined()s for:
>
> _POSIX_THREAD_PROCESS_SHARED
> _POSIX_THREAD_PRIO_PROTECT
> _POSIX_THREAD_PRIO_INHERIT
> _POSIX_THREAD_PRIORITY_SCHEDULING
>
> from our ?
Except for the first, which is left undefined in becau
On Fri, 18 Feb 2000, Bruce Evans wrote:
> On Thu, 17 Feb 2000, Daniel Eischen wrote:
>
> > On Thu, 17 Feb 2000, Thimble Smith wrote:
> >
> > > Hi. I recently updated from -stable to -current. I notice now that
> > > pthread.h relies on #defines that are in unistd.h; so in order to use
> > > p
On Thu, 17 Feb 2000, Daniel Eischen wrote:
> On Thu, 17 Feb 2000, Thimble Smith wrote:
>
> > Hi. I recently updated from -stable to -current. I notice now that
> > pthread.h relies on #defines that are in unistd.h; so in order to use
> > pthread_attr_setscope you have to include unistd.h befor
On Thu, 17 Feb 2000, Thimble Smith wrote:
> Hi. I recently updated from -stable to -current. I notice now that
> pthread.h relies on #defines that are in unistd.h; so in order to use
> pthread_attr_setscope you have to include unistd.h before pthread.h.
>
> Is this standard behaviour? I'm wor
Hi. I recently updated from -stable to -current. I notice now that
pthread.h relies on #defines that are in unistd.h; so in order to use
pthread_attr_setscope you have to include unistd.h before pthread.h.
Is this standard behaviour? I'm working with MySQL, and unistd.h is
included after pthre
