From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 0F92F1F506 for ; Thu, 22 Sep 2022 18:56:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230294AbiIVSzw convert rfc822-to-8bit (ORCPT ); Thu, 22 Sep 2022 14:55:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34770 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231185AbiIVSzt (ORCPT ); Thu, 22 Sep 2022 14:55:49 -0400 Received: from elephants.elehost.com (elephants.elehost.com [216.66.27.132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 87F619DFB9 for ; Thu, 22 Sep 2022 11:55:47 -0700 (PDT) Received: from Mazikeen (cpebc4dfb928313-cmbc4dfb928310.cpe.net.cable.rogers.com [99.228.251.108] (may be forged)) (authenticated bits=0) by elephants.elehost.com (8.16.1/8.16.1) with ESMTPSA id 28MItk3E067039 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Sep 2022 14:55:46 -0400 (EDT) (envelope-from rsbecker@nexbridge.com) Reply-To: From: To: "'Lana Deere'" , References: In-Reply-To: Subject: RE: 2.38.0 rc1 and explicit openssl version Date: Thu, 22 Sep 2022 14:55:41 -0400 Organization: Nexbridge Inc. Message-ID: <022d01d8ceb4$eccf3fb0$c66dbf10$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQFmWOWrQEfqmn9vGl1ETNbEXi/dRq7QtkVQ Content-Language: en-ca Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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=/openssl/3.0.5". As expected, configure reported > configure: Setting OPENSSLDIR to/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/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