Hello, thanks for testing!
Regarding the build failure when using LibreSSL, I can reproduce on OpenBSD: it's because the bundled libtls is meant to be used with OpenSSL. I'll take a look at having it build with LibreSSL too but that's more a quality-check rather than a priority since LibreSSL already ships libtls (or it should be.) What's interesting is why the configure is not picking up libtls from your LibreSSL installation. Probably you can 'force' it by setting CFLAGS/LDFLAGS pointing at the local libressl installation, but it shouldn't be necessary. Can you please share (off-list) the config.log? On 2023/06/05 15:20:38 -0700, Andi Vajda <o...@ovaltofu.org> wrote: > > On Mon, 5 Jun 2023, Andi Vajda wrote: > > > The build succeeds but running a debug session: > > sudo ./local/sbin/smtpd -f `pwd`/smtpd.conf -dv > > > > fails. I'm not sure how much of my debug logs is appropriate to post here > > but > > I could try to build with openssl 3 next ? > > Same problem with smtpd built with openssl 3.3.1: build succeeds, smtpd.conf > is validated OK when running with -n but when I start a debug session with > -dv, the server starts but eventually fails but is not saying much about > what is failing. It looks like a child process is terminating: > warn: lost child: dispatcher terminated; signal 11 > I also tried without --with-libevent=/usr/pkg > (and yes, I did not forget to stop my 6.8.0p2 server first) This also shouldn't happen. Is signal 11 SIGSEGV on NetBSD too? Can you share the config.log of this configuration too and smtpd complete log? Do you also get a core file? A backtrace would be incredibly useful. Thank you! Omar Polo
