fixCr compile failure about kent

[NullModel]

Good Morning Freedog8:

This is a puzzle, for sure. If I understand you correctly, you have built locally installed ssl libraries and are not using the system installed libraries. Correct ?

There are a number of ways to get around this situation.
Do you know if the pre-built binaries will function on your system
available at: http://hgdownload.cse.ucsc.edu/admin/exe/linux.x86_64/
or from http://hgdownload.cse.ucsc.edu/admin/exe/macOSX.x86_64/

This would save you the time building these on your system.

If your OS will not operate the binaries, you could use the gBiB
virtual machine if you happen to have VirtualBox available
on your system: http://genome.ucsc.edu/goldenpath/help/gbib.html

The problem you describe can be due to a number of different reasons.
The kent code uses both the SSL library functions and the CRYPTO
library functions. There could be confusion of where the include
files for these functions were picked up by the kent source build.
If the build used something other than you custom built libraries, they
might be mixed up. The error indicates the desired functions are
not found in the libraries specified: -L/home/O_O/local/lib -lpthread -lssl -lcrypto

There are many ways to run the compile link command, here is one example:

cc -O -g -o /cluster/home/hiram/bin/x86_64/fixCr fixCr.o ../../lib/x86_64/jkweb.a /usr/lib64/libmysqlclient.a /usr/lib64/libssl.a /usr/lib64/libcrypto.a -lkrb5 -ldl -lz /usr/lib/gcc/x86_64-redhat-linux/4.8.5/libstdc++.a /usr/lib64/librt.a -lpthread /usr/lib64/libssl.a /usr/lib64/libcrypto.a -lkrb5 -lk5crypto -ldl ../../htslib/libhts.a /usr/lib64/libpng.a -lm /usr/lib64/libz.a

Note the use of the static libraries. If you have static libraries available, try
to link with them in this order of this example.

Have you tried the 'userApps' procedure which is a bit more lightweight
compared to building the entire source tree:
https://genome-source.gi.ucsc.edu/gitlist/kent.git/tree/master/src/userApps/

[nathanweeks]

This is at least partially a real issue, as CRYPTO_set_locking_callback() was removed in OpenSSL 1.1.0 (openssl/openssl#1260). It's probably worth supporting both OpenSSL variants in kent/src/lib/https.c via #ifdef blocks.