Hi Steve, I get that maybe compilation is made problematic to prevent "no-tlsext" to be used, but what I think is why is it problematic only on Win32 and Win64 systems, compilation with the "no-tlsext" flag is not problematic on an HPUX system, I was able to build it without any issues.
On analysing the build I found out that,ssleay.def is created which has a list of all the functions that are to be exported in the ssleay.dll which is getting created. The list of functions are obtained by parsing the header files and finding the list of prototyped functions,even though the no-tlsext flag was given in ssl.h the 3 functions under suspicion were getting declared and as a result they were showing up in the def file even though they were not getting built, after the declaration of these functions was put under the OPENSSL_NO_TLSEXT macro check block, when the no-tlsext flag was defined, these functions ceased to exist and did not turn up in the .def file and as a result the linker did not throw an error. Is this an acceptable workaround, even if I am aware of the implications of using the "no-tlsext" flag? Regards Ashish ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
