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.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 9358B1F506 for ; Thu, 22 Sep 2022 18:48:54 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=pobox.com header.i=@pobox.com header.b="hFx7HP4Z"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231178AbiIVSst (ORCPT ); Thu, 22 Sep 2022 14:48:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54062 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232415AbiIVSsm (ORCPT ); Thu, 22 Sep 2022 14:48:42 -0400 Received: from pb-smtp21.pobox.com (pb-smtp21.pobox.com [173.228.157.53]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 36DB9E6A30 for ; Thu, 22 Sep 2022 11:48:39 -0700 (PDT) Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 930F31BB6C6; Thu, 22 Sep 2022 14:48:38 -0400 (EDT) (envelope-from tmz@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=date:from :to:cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=sasl; bh=3RBdvc4U391ksb9h6WAxd9lp9tSqPDs1P31O514 KbFk=; b=hFx7HP4Zw8iGi3yMxkhYbXhU0e7e3Ax9yDaP6ZO7Cf2lvo6oSis80oR 89B2Eb1o9k4FnD+p80BWj85PNwmo5kmiW1OK1PHLkAUFGVUwFCASwmYEi6Z2FoYC 2gu/fREjczrPEDlu+nXRKE5Ck9Jt1vcHVBUtKIYkO0A78MKvWuOQ= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 8BEE61BB6C5; Thu, 22 Sep 2022 14:48:38 -0400 (EDT) (envelope-from tmz@pobox.com) Received: from pobox.com (unknown [71.254.192.78]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 030A41BB6C4; Thu, 22 Sep 2022 14:48:33 -0400 (EDT) (envelope-from tmz@pobox.com) Date: Thu, 22 Sep 2022 14:48:30 -0400 From: Todd Zullinger To: Lana Deere Cc: git@vger.kernel.org Subject: Re: 2.38.0 rc1 and explicit openssl version Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Pobox-Relay-ID: 2918F1BA-3AA7-11ED-A201-B31D44D1D7AA-09356542!pb-smtp21.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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. 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