Build script is installing openssl pkg on FreeBSD 11.1

wattie

Verified User
Joined
May 31, 2008
Messages
1,234
Location
Bulgaria
I recently saw that I have openssl added in ports and I thought that I do not use it at all (FreeBSD have openssl in base by default and my ports are compiled against it).

I removed the port. Then I saw that it is being automatically installed again by the build script:

root@srv2:/usr/local/directadmin/custombuild # ./build update
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
openssl: 1.0.2o_4,1

Number of packages to be installed: 1

The process will require 12 MiB more space.
[1/1] Installing openssl-1.0.2o_4,1...
[1/1] Extracting openssl-1.0.2o_4,1: 100%
Message from openssl-1.0.2o_4,1:

Edit /usr/local/openssl/openssl.cnf to fit your needs.
./custombuild.tar.gz 100% of 195 kB 1720 kBps 00m00s
Extracting custombuild.tar.gz...
x custombuild/
...

It is probably coming from this part of the code:

Code:
                if [ ${MAINVER} -ge 10 ]; then
                        # Fixes apache OpenSSL problem: /usr/include/openssl/bn.h:603:1: error: unknown type name 'CRYPTO_THREADID'
                        if [ ! -d /usr/local/openssl ]; then
                                ${PKG_INSTALL} openssl
                        fi
                fi

Now my questions:

1. Is DA actually configuring the packages to use the OpenSSL from ports and not the base version, or this is some apache specific "hack"?

2. If so, can I go ahead and directly switch to the ports openssl in make.conf without breaking anything (from the DA packages I mean - I know I need to recompile the ports that are dependent on openssl)?
 
Last edited:
Back
Top