Static Linking git for HPE NonStop

Static Linking git for HPE NonStop

[Randall S. Becker]

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.

Re: Static Linking git for HPE NonStop

[Junio C Hamano]

"Randall S. Becker" <rsbecker@nexbridge.com> 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.

RE: Static Linking git for HPE NonStop

[Randall S. Becker]

On June 26, 2020 5:14 PM, Junio C Hamano wrote:
> "Randall S. Becker" <rsbecker@nexbridge.com> 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