Fixing a problem where the detection of openssl failed on solaris #468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Quick and dirty fix to resolve issue in compiling on Solaris fails.
There might be a longer more exhaustive fixed needed here. This is because Solaris 11.4 has two versions of openssl installed. The default one is
library/security/openssl
library/security/openssl-11
They are both installed (by default I think), and the 1.0.2 version is compiled to use for application with FIPS certification requirements. We should probably link to the newer one openssl-11, but the paths aren't setup correctly for this, e.g. /usr/include/openssl points to /usr/openssl/default/include via symlink by default.
Users on Solaris 11.4 should be aware that the way to configure this using the openssl-11 libraries would be to pass the correct
--with-openssl=/usr/openssl/1.1
to the configure (or autogen.sh) command.