make pkg support FreeBSD base with privatessl #1328
Conversation
checking for library containing SHA256_Init... no checking for library containing SHA256_Init... (cached) no configure: error: unable to find the libcrypto The second time autoconf will use the cached negative result, and not locate the library by the alternative name
|
ok to test |
|
If you re-base this to pull in the changes that I did to fix the travis-ci tests, I think it might pass the tests. |
|
Can one of the admins verify this patch? |
|
are we still planning for a privatessl? |
It is a best way to resolve dll hell with ports ssl -- even if use staged open/libre ssl for static build, ld is always checks for functions presence in base libss/libcrypto :( If anyone interested, privatessl patch revisited: |
|
@fluffykhv right but have you tested your approach with an exp-run? how do you deal with kerberos? are ports linked to base kerberos still working if it is linked to a base openssl? |
|
@bapt working on kerberos now. base heimdail is a pain in ass :( looks like base kerberos libs need to be hided too, and all ports switch over to ports crypto/ssl/krb :( |
This allows pkg to find hidden "private" libssl and libcrypto on FreeBSD, as openssl is transitioned to being private.