{"thread":{"id":"58496","subject":"2.38.0 rc1 and explicit openssl version","startedAt":"2022-09-22T18:36:26Z","lastAt":"2022-09-22T18:55:54Z","messageCount":3,"participants":["Lana Deere","Todd Zullinger","rsbecker@nexbridge.com"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"463458","messageId":"CA+4x=b-myNFKfN1n1jrU+wMYfXbA7VrnrKVi7vj9LU4E9wb_rw@mail.gmail.com","threadId":"58496","inReplyTo":null,"subject":"2.38.0 rc1 and explicit openssl version","fromName":"Lana Deere","fromEmail":"lana.deere@gmail.com","sentAt":"2022-09-22T18:35:45Z","receivedAt":"2022-09-22T18:36:26Z","isPatch":false,"sender":{"key":"lana.deere@gmail.com","avatar":null},"body":"I built 2.38.0 rc1 from the tar file today.  One of the configure\noptions I used was \"--with-openssl=<path>/openssl/3.0.5\".  As\nexpected, configure reported\n    configure: Setting OPENSSLDIR to<path>/openssl/3.0.5\n\nWhen it got as far as linking git-imap-send, the link command pointed\nat the subdirectory \"lib\" within the openssl/3.0.5 installation.\n    gcc ... -o git-imap-send ...  -L<path>/openssl/3.0.5/lib ...\n\nHowever, this version of openssl put the libraries into a \"lib64\"\nsubdirerctory rather than into a \"lib\" subdirectory so the link\nfailed.  An easy workaround is to put a symlink from lib64 to lib\ninside the openssl directory.  It would be nice, though, if the\nconfigure command could figure this out automatically.\n\n.. Lana (lana.deere@gmail.com)\n"},{"id":"463460","messageId":"Yyyt/reX3mcYK+1Q@pobox.com","threadId":"58496","inReplyTo":"CA+4x=b-myNFKfN1n1jrU+wMYfXbA7VrnrKVi7vj9LU4E9wb_rw@mail.gmail.com","subject":"Re: 2.38.0 rc1 and explicit openssl version","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2022-09-22T18:48:30Z","receivedAt":"2022-09-22T18:48:50Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Lana Deere wrote:\n> I built 2.38.0 rc1 from the tar file today.  One of the configure\n> options I used was \"--with-openssl=<path>/openssl/3.0.5\".  As\n> expected, configure reported\n>     configure: Setting OPENSSLDIR to<path>/openssl/3.0.5\n> \n> When it got as far as linking git-imap-send, the link command pointed\n> at the subdirectory \"lib\" within the openssl/3.0.5 installation.\n>     gcc ... -o git-imap-send ...  -L<path>/openssl/3.0.5/lib ...\n> \n> However, this version of openssl put the libraries into a \"lib64\"\n> subdirerctory rather than into a \"lib\" subdirectory so the link\n> failed.  An easy workaround is to put a symlink from lib64 to lib\n> inside the openssl directory.  It would be nice, though, if the\n> configure command could figure this out automatically.\n\nI don't use the configure script, but I think you can\nspecify the lib dir via --with-lib=lib64.  (The same can be\ndone using config.mak or passing parameters directly to\nmake with the lib argument, e.g. make lib=lib64 ...)\n\nIf I'm reading correctly, that would apply to all packages\nwhich were configured via one of the --with-$package=$path\noptions.\n\n-- \nTodd\n"},{"id":"463461","messageId":"022d01d8ceb4$eccf3fb0$c66dbf10$@nexbridge.com","threadId":"58496","inReplyTo":"CA+4x=b-myNFKfN1n1jrU+wMYfXbA7VrnrKVi7vj9LU4E9wb_rw@mail.gmail.com","subject":"RE: 2.38.0 rc1 and explicit openssl version","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2022-09-22T18:55:41Z","receivedAt":"2022-09-22T18:55:54Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On September 22, 2022 2:36 PM, Lana Deere wrote:\n>I built 2.38.0 rc1 from the tar file today.  One of the configure options I used was \"-\n>-with-openssl=<path>/openssl/3.0.5\".  As expected, configure reported\n>    configure: Setting OPENSSLDIR to<path>/openssl/3.0.5\n>\n>When it got as far as linking git-imap-send, the link command pointed at the\n>subdirectory \"lib\" within the openssl/3.0.5 installation.\n>    gcc ... -o git-imap-send ...  -L<path>/openssl/3.0.5/lib ...\n>\n>However, this version of openssl put the libraries into a \"lib64\"\n>subdirerctory rather than into a \"lib\" subdirectory so the link failed.  An easy\n>workaround is to put a symlink from lib64 to lib inside the openssl directory.  It\n>would be nice, though, if the configure command could figure this out\n>automatically.\n\nThe 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.\n\nRegards,\nRandall\n\n"}]}