24 Mar
2011
24 Mar
'11
11:36 a.m.
It's the other way around - I changed Boost.Config to set BOOST_NO_FENV_H for Intel prior to 12.0 because it fails the test case (calls to fenv.h functions seem to pretty much always return an error code - it's not at all clear that fenv.h is really working for that compiler). Unfortunately this broke Boost.Test.... but I also committed a fix for that yesterday, so hopefully all will be back to normal soon! Apologies for the problem, John.
OK, no problem for me. I'll denote this compiler as unsupported then.
Is there a fallback for systems with no fenv.h? If so the right thing to do is to check for BOOST_NO_FENV_H before including the detail/ header (not sure what use the detail/ header is in that case, but there you go...) John.