Hi Brad, thanks for pointing me to the report. I should have searched myself:) The POSIX alternative to the self pipe trick is using a pselect In [1] is an article on LWN about it.
Best Dimitar 1 - https://lwn.net/Articles/176911/ * Brad King <brad.k...@kitware.com> [16-06-03 17:00 CEST]: > On 06/03/2016 02:05 AM, Yordanov, Dimitar wrote: > >> Are you running inside some kind of virtualization or emulation > >> environment? > > > > Actually not. The server is maybe under heavy load, but should it > > matter? > > See discussion here: > > https://cmake.org/Bug/view.php?id=15873 > > > Possibly I'm on the wrong track, but couldn't the compiler reorder the > > code where kwsysProcess is set, and move it out of the blocked > > section? Should it be volatile to avoid such scenario? > > I think further investigation/debugging would be needed to answer that. > > > I thought (void)write(...); is a portable way to say that we are not > > interested in the return value. Not that I would change running code > > for that. > > I think we used to have that and some compilers warned anyway. > > -Brad > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
