Re: [Fetchmail-users] build errors for fetchmail-6.4.8

[Peter S. <dr...@uc...>]

Dear Matthias,

Thanks for your note, with its suggestion to try adding
"--with-ssl=/opt/openssl" to the ./configure command.

It turns out that did not help, so I will abandon my attempts to
compile fetchmail-6.4.8 on my ancient Scientific Linux 6.10 OS,
where by necessity there is the older openssl-1.0.1e-fips
in addition to openssl-1.1.1g.

I'm in the process of migrating to Fedora 32 on a new drive
(where everything works much more smoothly), and arranging new
email there, with sendmail, fetchmail, procmail, bogofilter and
mutt, all quite speedy and working well.

Thanks so much,

     -- Peter

=================================================================
On Jul 03, 2020 at 11:04 pm, Matthias Andree <mat...@gm...> wrote:
| Am 03.07.20 um 22:32 schrieb Peter Scott:
| > Dear Matthias,
| >
| > Sure, feel free to quote anything you like on the list.  [...]
| 
| Peter,
| 
| Thanks for the permission to answer in public.
| 
| > On Fri, Jul 3, 2020 at 8:50 AM Matthias Andree <mat...@gm...
| > <mailto:mat...@gm...>> wrote:
| >
| >     Peter,
| >
| >     can I fullquote and answer on the mailing list, please?
| >     [...]
| >
| >     It might also help if you re-sent your previous mail to the list
| >     instead, so we get the solution into the archives.
| >
| >     Regards
| >     Matthias
| >
| >     Am 02.07.20 um 23:29 schrieb Peter Scott:
| >     > Matthias,
| >     >
| >     > Thanks for your comments.  I suspect my problem is that I have two
| >     > versions of openssl.
| >     > My OS is Scientific Linux-6.10 (like RHEL-6 or CentOS-6) for
| >     which the
| >     > openssl (shipped) version is OpenSSL 1.0.1e-fips 11 Feb 2013.
| >     > This is too old for fetchmail-6.4.8.
| >     > So I got the source for OpenSSL 1.1.1g  21 Apr 2020, which compiled
| >     > and installed in /opt/openssl with no glitches, and seems to work.
| >     >
| >     > Then to configure and build fetchmail-6.4.8, I first exported
| >     > LD_LIBRARY_PATH=/opt/openssl/lib and PATH=/opt/openssl/bin:$PATH.
| >     > Then for fetchmail-6.4.8, I did ./configure --prefix=$HOME.  This
| >     > completed, however there are these suspicious lines, especially
| >     > the WARNING line, and the first line below referring to a pkg-config
| >     > binary.
| >
| So the thing is if the system has multiple implementations, then it's in
| for a bit of a rough ride because I suppose you don't have a pkg-config
| in /opt/openssl/bin. So I think it's worth trying to add
| "--with-ssl=/opt/openssl" to the ./configure command line and retry from
| there. If it doesn't work, I'll need the full config.log to analyze
| whether configure is doing the right thing (given my other commitments
| over the next days, paste to https://paste.debian.net/ and please set
| expiry to 90 days so it's still there when I have time to look).
| 
| >     >
| >     > checking for pkg-config... /usr/bin/pkg-config
| >     > checking pkg-config is at least version 0.9.0... yes
| >     > checking for SSL... yes
| >     > configure: Enabling SSL support.
| >     > checking whether TLS1_3_VERSION is declared... no
| >     > configure: WARNING: Your OpenSSL version is too old and does not
| >     > support TLS v1.3. Upgrade.
| >
| This is a hint it picked up the older OpenSSL 1.0.x.
| 
| 
| >     >
| >     > So my question: Is there anything I can add to the ./configure that
| >     > will demand that the appropriate
| >     > openssl libraries will be consulted?  (I'm thinking that
| >     > /usr/bin/pkg-config finds the wrong libraries.)
| >
| Yes. ./configure --your --other --options --with-ssl=/opt/openssl might
| do the trick. If pkg-config picks up the wrong version again, you may
| need to temporarily deinstall it during ./configure, as a workaround -
| then I'll definitely need the full config.log as written above so I can
| try to find the bug and remove it.
| 
| 
| 
|