Bug 235248 - news/nzbget: build failure under 12.0 with openssl from ports, CRYPT_num_locks missing
Summary: news/nzbget: build failure under 12.0 with openssl from ports, CRYPT_num_lock...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-27 16:12 UTC by Phillip R. Jaenke
Modified: 2019-07-28 21:14 UTC (History)
0 users

See Also:


Attachments
news_nzbget.build.log (100.30 KB, text/plain)
2019-01-27 16:12 UTC, Phillip R. Jaenke
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Phillip R. Jaenke 2019-01-27 16:12:05 UTC
Created attachment 201452 [details]
news_nzbget.build.log

nzbget has not been building on 12.0 for some time now. Missing symbol error, specifically CRYPTO_num_locks
Comment 1 Phillip R. Jaenke 2019-01-27 16:14:09 UTC
Sorry, I forgot to note the make.conf:

## Define our default versions
DEFAULT_VERSIONS+=perl5=5.26
DEFAULT_VERSIONS+=ruby=2.3
DEFAULT_VERSIONS+=python2=2.7
DEFAULT_VERSIONS+=python3=3.6
DEFAULT_VERSIONS+=lua=5.2

DEFAULT_VERSIONS+=pgsql=10
DEFAULT_VERSIONS+=mysql=10.1m

DEFAULT_VERSIONS+=apache=2.4
DEFAULT_VERSIONS+=php=7.2
DEFAULT_VERSIONS+=samba=4.8

## Use OpenSSL from ports.
DEFAULT_VERSIONS+=ssl=openssl
security_openssl_SET+=RC5
Comment 2 Phillip R. Jaenke 2019-01-28 07:35:13 UTC
Did some additional tracking down, this is most definitely related to disabling SSLv3 in security/openssl, which has not been done in base. 

The inflection commit for security/openssl is r406060 adding the SSL3 disable option.

Here's where it gets broken; OPTIONS+=SSL3 is on by default in security/openssl, so it should be working. I confirmed my options on security/openssl and reset to defaults. Same result; CRYPT_num_locks missing. Even though SSL3 is on in security/openssl. The symptom says "you disabled SSLv3" and the strings say as much with the output of security/openssl. But it was not disabled in the build. This may go to security/openssl itself.