From: Todd Zullinger <tmz@pobox.com>
To: Lana Deere <lana.deere@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: 2.38.0 rc1 and explicit openssl version
Date: Thu, 22 Sep 2022 14:48:30 -0400 [thread overview]
Message-ID: <Yyyt/reX3mcYK+1Q@pobox.com> (raw)
In-Reply-To: <CA+4x=b-myNFKfN1n1jrU+wMYfXbA7VrnrKVi7vj9LU4E9wb_rw@mail.gmail.com>
Lana Deere wrote:
> 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
next prev parent reply other threads:[~2022-09-22 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 18:35 2.38.0 rc1 and explicit openssl version Lana Deere
2022-09-22 18:48 ` Todd Zullinger [this message]
2022-09-22 18:55 ` rsbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yyyt/reX3mcYK+1Q@pobox.com \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=lana.deere@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).