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-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id BBD2E1F5AE for ; Fri, 26 Jun 2020 20:33:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725806AbgFZUdN (ORCPT ); Fri, 26 Jun 2020 16:33:13 -0400 Received: from elephants.elehost.com ([216.66.27.132]:15992 "EHLO elephants.elehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725780AbgFZUdN (ORCPT ); Fri, 26 Jun 2020 16:33:13 -0400 X-Virus-Scanned: amavisd-new at elehost.com Received: from gnash (CPE00fc8d49d843-CM00fc8d49d840.cpe.net.cable.rogers.com [173.32.57.223]) (authenticated bits=0) by elephants.elehost.com (8.15.2/8.15.2) with ESMTPSA id 05QKXAKh043243 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 26 Jun 2020 16:33:11 -0400 (EDT) (envelope-from rsbecker@nexbridge.com) From: "Randall S. Becker" To: Subject: Static Linking git for HPE NonStop Date: Fri, 26 Jun 2020 16:33:05 -0400 Message-ID: <011901d64bf9$0235d2b0$06a17810$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-ca Thread-Index: AdZL+HZ3rZi3NafZSLW5IggfV+634A== Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi Team, I am faced with a bit of a conundrum. There are multiple implementations of SSL on our platform that co-exist in some installations. While it is possible to select which one is used, it becomes difficult with other subsystems are at play, including Jenkins. Is there anyway to force a static linkage instead of using DLLs so that we can isolate this for installations who want to be insulated from the confusion? We currently have everything encoded in config.mak.uname and do not use make configure or configure explicitly. Just make. Thanks, Randall -- Brief whoami: NonStop developer since approximately 211288444200000000 UNIX developer since approximately 421664400 -- In my real life, I talk too much.