Kevin Harris wrote:
I'm trying to update my project to use boost 1.35. There is behavior in the test library to catch SIGCHLD and consider it an error. Is there a reason for this?
Jens Seidel replied:
This is an error which is already fixed in trunk. I suggest you try it out so that further related bugs can be fixed in time.
There appears to be a related compile error, currently in the trunk: ../boost/test/impl/execution_monitor.ipp: In member function 'void boost::detail::system_signal_exception::report() const': ../boost/test/impl/execution_monitor.ipp:443: error: 'SIGPOLL' was not declared in this scope ../boost/test/impl/execution_monitor.ipp:470: error: duplicate case value ../boost/test/impl/execution_monitor.ipp:460: error: previously used here ../boost/test/impl/execution_monitor.ipp: In constructor 'boost::detail::signal_handler::signal_handler(bool, int, bool, char*)': ../boost/test/impl/execution_monitor.ipp:627: error: 'SIGPOLL' was not declared in this scope http://www.boost.org/development/tests/trunk/output/Oliver%20Baltzer-boost-b... Does anyone know how to fix it? (I'm clueless, but it looks like a missing #include.) -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center