checking for library containing BIO_new... -lcrypto checking for library containing SSL_library_init... no configure: error: "libssl not found" !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-mail/fdm-1.9/work/fdm-1.9/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_20190205-121519 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) * Available Rust versions: [1] rust-1.32.0 * emerge -qpvO net-mail/fdm [ebuild N ] net-mail/fdm-1.9 USE="pcre -courierauth -examples -libressl"
Created attachment 564212 [details] emerge-info.txt
Created attachment 564214 [details] emerge-history.txt
Created attachment 564216 [details] environment
Created attachment 564218 [details] etc.portage.tbz2
Created attachment 564220 [details] logs.tbz2
Created attachment 564222 [details] net-mail:fdm-1.9:20190208-080305.log
Created attachment 564224 [details] temp.tbz2
Issue is that SSL_library_init() is now (openssl-1.1.1, maybe even -1.1.0) a macro defined in <openssl/ssl.h>, but fdm's configure.ac tries to find it using AC_SEARCH_LIBS, which assumes that it is an actual symbol in the .so for the library. Proper fix is to have upstream use a different AC_SEARCH_LIBS invocation to detect the presence of the openssl library. A work-around is to replace "char SSL_library_init ();" with "#include <openssl/ssl.h>" in the "configure" script (this is brittle, however, in that a re-invocation of autoconf will clobber the "fix").
Created attachment 565570 [details, diff] work-around patch to get fdm-1.9 to compile against openssl-1.1*
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5372dc2164679ced7d53b2918059f1dfc76b5ea8 commit 5372dc2164679ced7d53b2918059f1dfc76b5ea8 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2019-06-25 14:27:39 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2019-06-25 14:28:53 +0000 net-mail/fdm: new version 2.0. This new version is intended to fix bug 677484 that is killing the build. The previous version is a few years old, and an upgrade is probably easier than patching. The new version also has some other improvements: * Courier support was dropped (upstream commit bc34a567). * The ./configure script now supports --enable-pcre instead of passing PCRE=1 to "make". * The build system installs stuff into the correct locations without us passing variables to "make install". * User creation has been moved to pkg_preinst() since the user is only needed at runtime. * Use EAPI=7. * Drop unused eutils, multilib, and toolchain-funcs eclasses. Bug: https://bugs.gentoo.org/677484 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> Package-Manager: Portage-2.3.66, Repoman-2.3.11 net-mail/fdm/Manifest | 1 + net-mail/fdm/fdm-2.0.ebuild | 42 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+)
It was easier to add v2.0 than to try to fix this in v1.9. Please test and let me know if it fixes the problem.
(In reply to Michael Orlitzky from comment #11) > It was easier to add v2.0 than to try to fix this in v1.9. Please test and > let me know if it fixes the problem. Seems to be working fine, thanks!
(In reply to Alec Moskvin from comment #12) > > Seems to be working fine, thanks! Glad to hear it. We'll also need fdm-2.0 to go stable when openssl-1.1 does, but for now this is fixed (you should be fine if you stick to either ~arch or stable). If anyone remembers, feel free to ping me about stabilization when the time comes.
