P Kamath wrote: > " > I don't think you can avoid a dependency on the system threading > library > though, but I don't see why that would be an issue. Many single- > threaded > programs wind up requiring the threading library on many platforms > anyway > as > it may contain functions like 'clock_gettime' or 'sched_yield'. (Does > anyone > know of a platform where this is a problem?) > " > Alas, yes HP/UX. > Link code built threaded and code built unthreaded on that platform and > your application dies a horrible death.
That's not a problem. On those platforms, you have to a single-threaded and a multi-threaded build of the library anyway. The single-threaded build requires no thread safety features. The multi-threaded build can safely refer to symbols in the threading library. The problem case would be a platform where you could have code that was safe to use in both single-threaded and multi-threaded applications, but it would cause an issue (for single-threaded applications/libraries) if it referenced symbols in the threading library (but didn't call them at run time). DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
