Re: 2.38.0 rc1 and explicit openssl version

From: Todd Zullinger <tmz@pobox.com>
Date: Sep 22, 2022, 18:48 UTC
Message-ID: <Yyyt/reX3mcYK+1Q@pobox.com>
In-Reply-To: <CA+4x=b-myNFKfN1n1jrU+wMYfXbA7VrnrKVi7vj9LU4E9wb_rw@mail.gmail.com>

Lana Deere wrote:

Show 14 quoted lines

> I built 2.38.0 rc1 from the tar file today.  One of the configure
> options I used was "--with-openssl=<path>/openssl/3.0.5".  As
> expected, configure reported
>     configure: Setting OPENSSLDIR to<path>/openssl/3.0.5
> 
> When it got as far as linking git-imap-send, the link command pointed
> at the subdirectory "lib" within the openssl/3.0.5 installation.
>     gcc ... -o git-imap-send ...  -L<path>/openssl/3.0.5/lib ...
> 
> However, this version of openssl put the libraries into a "lib64"
> subdirerctory rather than into a "lib" subdirectory so the link
> failed.  An easy workaround is to put a symlink from lib64 to lib
> inside the openssl directory.  It would be nice, though, if the
> configure command could figure this out automatically.

I don't use the configure script, but I think you can specify the lib dir via --with-lib=lib64. (The same can be done using config.mak or passing parameters directly to make with the lib argument, e.g. make lib=lib64 ...)

If I'm reading correctly, that would apply to all packages which were configured via one of the --with-$package=$path options.

-- 
Todd