On 23 Oct 2020, at 16:20, Pablo Murillo (rednet) via spamdyke-users
wrote:
I applied your patches on the source files, compile with TLS support,
and the program was compiled, yes, but, without TLS support
I checked the patches before compile and I saw that the only thing you
did (about TLS) was to remove all the lines where TLS is added
Sorry, this is not correct. The patches to configure (and configure.ac)
are to "Remove outdated OpenSSL check to build with OpenSSL 1.1.x." They
remove a check that fails with OpenSSL 1.1.x, so that --enable-tls can
work. The check should probably be updated, not removed, but since
pkgsrc always explicitly passes --disable-tls or --enable-tls (after
arranging for OpenSSL libs and headers to be absent or present), I
didn't want to invest any more effort here.
The patch to tls.c is to "Support OpenSSL 1.1.x.". It's a very small
patch. What was called "SSL_library_init()" in older OpenSSL is now
pronounced "OPENSSL_init_ssl(0, NULL)". All the other OpenSSL API calls
continue to build as is.
This is not a patch to compile whit tls, the result is the same
compiling without tls support
Here's what I get:
$ uname -v
FreeBSD 12.1-RELEASE-p10 GENERIC
$ cd ~/trees/pkgsrc-current/mail/spamdyke
$ make show-options
Any of the following general options may be selected:
tls Enable TLS support.
These options are enabled by default:
These options are currently enabled:
tls
You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or PKG_OPTIONS.spamdyke.
$ make install clean
[...]
$ ldd /opt/pkg/bin/spamdyke
/opt/pkg/bin/spamdyke:
libcrypto.so.111 => /lib/libcrypto.so.111 (0x800297000)
libc.so.7 => /lib/libc.so.7 (0x800586000)
libthr.so.3 => /lib/libthr.so.3 (0x80097f000)
If you can't reproduce this result without pkgsrc, but you need to be
able to build spamdyke with OpenSSL on FreeBSD, I suggest you try
pkgsrc.
- Amitai
_______________________________________________
spamdyke-users mailing list
[email protected]
https://spamdyke.org/mailman/listinfo/spamdyke-users
