Hi Guys! On Mon, May 14, 2012 at 4:10 AM, Kai Tietz <[email protected]> wrote: > 2012/5/14 xunxun <[email protected]>: >> 于 2012/5/14 15:15, Ruben Van Boxem 写道: >>> I'll add that in my next build. The question becomes then why is this >>> not detected by configure automatically? >> Maybe Kai knows. >> >> This happened in gcc4.6.x first, so I use --enable-libstdcxx-time=yes >> from then. >> >> Best Regards, >> xunxun > > Well, AFAIU is libstdc++ here checking for presence of nanosleep. > Actual we provide '_sleep' (and usleep), but no nanosleep routine as > it is POSIX. If you are using winpthread then this routine is provide > by it, but of course it is just present if pthread is linked. > So --enable-libstdcxx-time=yes seems to me as valid and the best way > to solve this issue. > > Kai
Thanks for the follow-up. This is in no way urgent for me. Native windows Sleep is fine for me for the simple stuff I'm doing. But if you release another <thread>-enabled build with sleep_for included, I'll plan to give it a try. By the way, a quick semi-related question: To use native windows Sleep I am including windows.h. It's not a big deal, but it does increase the compile time of simple test programs noticeably. (Not really a lot, though.) Would anyone know off-hand if I can just put in two or three lines of prototype declarations for Sleep instead of including all of windows.h? Thanks to all. K. Frank ------------------------------------------------------------------------------ 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/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
