git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* 2.38.0 rc1 and explicit openssl version
@ 2022-09-22 18:35 Lana Deere
  2022-09-22 18:48 ` Todd Zullinger
  2022-09-22 18:55 ` rsbecker
  0 siblings, 2 replies; 3+ messages in thread
From: Lana Deere @ 2022-09-22 18:35 UTC (permalink / raw)
  To: git

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.

.. Lana (lana.deere@gmail.com)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.38.0 rc1 and explicit openssl version
  2022-09-22 18:35 2.38.0 rc1 and explicit openssl version Lana Deere
@ 2022-09-22 18:48 ` Todd Zullinger
  2022-09-22 18:55 ` rsbecker
  1 sibling, 0 replies; 3+ messages in thread
From: Todd Zullinger @ 2022-09-22 18:48 UTC (permalink / raw)
  To: Lana Deere; +Cc: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: 2.38.0 rc1 and explicit openssl version
  2022-09-22 18:35 2.38.0 rc1 and explicit openssl version Lana Deere
  2022-09-22 18:48 ` Todd Zullinger
@ 2022-09-22 18:55 ` rsbecker
  1 sibling, 0 replies; 3+ messages in thread
From: rsbecker @ 2022-09-22 18:55 UTC (permalink / raw)
  To: 'Lana Deere', git

On September 22, 2022 2:36 PM, 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.

The OpenSSL team moved the 64-bit builds to lib64 as of 3.0.x. This is very likely to be retained in 3.1.x. I am working on a change that moves the runnable parts of OpenSSL 64-bit to /bin64. The 32-bit builds are still in /lib and /bin. My team hit this issue when first trying to build git and curl with 3.0.1. We control where we pick up libraries on the make command line using the CFLAGS and LDFLAGS variables so the internal git makefile does not need to know where the libraries are. This also avoids needing symlinks that can cause DLL conflicts between 32 and 64 models.

Regards,
Randall


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-09-22 18:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-22 18:35 2.38.0 rc1 and explicit openssl version Lana Deere
2022-09-22 18:48 ` Todd Zullinger
2022-09-22 18:55 ` rsbecker

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).