Nelson, I don't have a libsectool.a anymore since NSS 3.3 now provides only 3 shared libs (nss3.dll, smime3.dll, ssl3.dll) Do I need to build a custom NSS 3.3 to export functions that are now internal? Which NSS build file do I need to tweak the directives for export NSS functions?
-- P "Nelson B. Bolyard" wrote: > Patrick wrote: > > > > Hello, > > > > How does one get error messages when using NSS3.3? The only NSS3.3 > > public function which could help is PORT_GetError, however it seems > > limited to NSPR type opreations. What about NSS/SSL error messages? > > The correct function to use is PR_GetError(). > The same error mechanism is used by NSPR and NSS. > > > My app used to use SECU_Strerror but that function is no gone or failed > > to be made public... > > SECU_Strerror is in libsectool.a (or sectool.lib on Windoze). > > -- > Nelson Bolyard Netscape Communications (subsidiary of AOL) > Disclaimer: I speak for myself, not for Netscape
