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 pthread.h; should I have that code changed, or should FreeBSD somehow compensate for this? Thanks, Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: pthread.h and unistd.h Thimble Smith
- Re: pthread.h and unistd.h Daniel Eischen
- Re: pthread.h and unistd.h Bruce Evans
- Re: pthread.h and unistd.h Daniel Eischen
- Re: pthread.h and unistd.h Bruce Evans
- Re: pthread.h and unistd.h Jason Evans