From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: <git@vger.kernel.org>
Subject: Re: Static Linking git for HPE NonStop
Date: Fri, 26 Jun 2020 14:13:43 -0700 [thread overview]
Message-ID: <xmqq366hh6ns.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <011901d64bf9$0235d2b0$06a17810$@nexbridge.com> (Randall S. Becker's message of "Fri, 26 Jun 2020 16:33:05 -0400")
"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.
next prev parent reply other threads:[~2020-06-26 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 20:33 Static Linking git for HPE NonStop Randall S. Becker
2020-06-26 21:13 ` Junio C Hamano [this message]
2020-06-26 21:26 ` Randall S. Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq366hh6ns.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).