>Is v3 explicitly calling a "long double" C library function that is >failing or not working in the "double" compatibility mode? Apparently. > I am not sure >what could cause "long double" to fail while the equivalent "double" >succeeds. I can't tell by just looking at the sources, sorry. -benjamin