It looks like one of <unistd.h> & <sys/syscall.h> is setting _XOPEN_SOURCE before we get a chance to do it in pthread_posix.c, and, on some versions of the pthread.h header, we need to have _XOPEN_SOURCE defined to the right value for pthread_mutexattr_settype and other items to become available.
We added the <unistd.h> & <sys/syscall.h> includes as part of the logging thread ID support [1], so this affects the 1.0.11 release as well (but not 1.0.10). Checking further, I'm seeing this occur on other recent Linux platforms (eg. Slackware 13.37), which makes me wonder if this may affect the Debian switch to libusbx. If all the recent versions of pthread.h are similar, I would expect them to run into the same issue. Sure wish we had Jenkins finalized, as we would have spotted this problem early... Now, I remember having issues with the order of the headers in pthread_posix.c as well (I think it was on OS-X), so sorting a patch may take a little while. I'll try to have something later on today. Regards, /Pete [1] http://libusbx.git.sourceforge.net/git/gitweb.cgi?p=libusbx/libusbx;a=commitdiff;h=463dda06db5da5de0eab32820c7af60605625afe#patch6 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusbx-devel
