Randall
2021-08-30 19:56:30 UTC
Hi Everyone,
We are a week or four (I'm not sure) away from the official OpenSSL 3.0.0a release. This release has some structural changes allowing the code to take up less space on your system if you run multiple memory models. The variant code will drop into the following lib directory:
/usr/local-ssl3.0/lib - 32-bit unthreaded
/usr/local-ssl3.0/lib64 - 64-bit unthreaded
/usr/local-ssl3.0/lib-spt - 32-bit SPT
/usr/local-ssl3.0/lib64-put - 64-bit PUT
There is also a ./providers area that is also similarly named.
This will allow the common stuff, like header files, certificates, and man pages, to reside in common directories. The only catch is that there is only one bin directory for now so your last install will be the model you use for the openssl application - I have contributed a change that should fix that (PR#16472 if you are monitoring). This particular change was done to make NonStop comply with Linux implementations and allow other Open-Source packages to find the correct OpenSSL libraries, which they currently do not do.
More to come.
Randall Becker
On Behalf of the ITUGLIB Technical Committee.
We are a week or four (I'm not sure) away from the official OpenSSL 3.0.0a release. This release has some structural changes allowing the code to take up less space on your system if you run multiple memory models. The variant code will drop into the following lib directory:
/usr/local-ssl3.0/lib - 32-bit unthreaded
/usr/local-ssl3.0/lib64 - 64-bit unthreaded
/usr/local-ssl3.0/lib-spt - 32-bit SPT
/usr/local-ssl3.0/lib64-put - 64-bit PUT
There is also a ./providers area that is also similarly named.
This will allow the common stuff, like header files, certificates, and man pages, to reside in common directories. The only catch is that there is only one bin directory for now so your last install will be the model you use for the openssl application - I have contributed a change that should fix that (PR#16472 if you are monitoring). This particular change was done to make NonStop comply with Linux implementations and allow other Open-Source packages to find the correct OpenSSL libraries, which they currently do not do.
More to come.
Randall Becker
On Behalf of the ITUGLIB Technical Committee.