If it defaults to NO in the unknown case and the accounting actually is thread local then there's a big risk that gethrvtime starts returning negative values.
The UNKNOWN case should never happen if the configure test works, but I wasn't sure enough of that. I made a fallback instead of an AC_MSG_ERROR since I thought it would be annoying if the builds fail utterly because of it.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-02-10 13:15: Subject: CPU_TIME_IS_THREAD_LOCAL
Is the UNKNOWN case meaningful? Shouldn't there be process global accounting in this case too? The global variable isn't even declared unless CPU_TIME_IS_THREAD_LOCAL has the value `NO'.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)