# Static Linking git for HPE NonStop 3 messages from 2020-06-26 to 2020-06-26. Participants: Randall S. Becker, Junio C Hamano. Thread: https://gitlist.dev/t/53763 ## Randall S. Becker, 2020-06-26 20:33 Subject: Static Linking git for HPE NonStop Message-ID: <011901d64bf9$0235d2b0$06a17810$@nexbridge.com> URL: https://gitlist.dev/e/011901d64bf9%240235d2b0%2406a17810%24%40nexbridge.com ``` 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. ``` ## Junio C Hamano, 2020-06-26 21:13 Subject: Re: Static Linking git for HPE NonStop Message-ID: URL: https://gitlist.dev/e/xmqq366hh6ns.fsf%40gitster.c.googlers.com In-Reply-To: <011901d64bf9$0235d2b0$06a17810$@nexbridge.com> ``` "Randall S. Becker" writes: > ... 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. A quick scan of our Makefile seems to say that LDFLAGS is left open for builder's use (i.e. we don't add hardcoded "always link dynamically" etc. in there, so that somebody doing a build for a particular use case can tell the linker "I want things linked statically" by adding appropriate and linker specific flags to it, and that propagates to ALL_LDFLAGS to be used at the last stage of linking the git binary itself. ``` ## Randall S. Becker, 2020-06-26 21:26 Subject: RE: Static Linking git for HPE NonStop Message-ID: <012601d64c00$6d366280$47a32780$@nexbridge.com> URL: https://gitlist.dev/e/012601d64c00%246d366280%2447a32780%24%40nexbridge.com In-Reply-To: ``` On June 26, 2020 5:14 PM, Junio C Hamano wrote: > "Randall S. Becker" writes: > > ... 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. > > A quick scan of our Makefile seems to say that LDFLAGS is left open for > builder's use (i.e. we don't add hardcoded "always link dynamically" etc. in > there, so that somebody doing a build for a particular use case can tell the > linker "I want things linked statically" by adding appropriate and linker > specific flags to it, and that propagates to ALL_LDFLAGS to be used at the > last stage of linking the git binary itself. Thanks. That would work just fine. Regards, Randall ```