git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: Static Linking git for HPE NonStop

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Jun 26, 2020, 21:26 UTC
Message-ID
<012601d64c00$6d366280$47a32780$@nexbridge.com>
In-Reply-To
<xmqq366hh6ns.fsf@gitster.c.googlers.com>
On June 26, 2020 5:14 PM, Junio C Hamano wrote:
Show 10 quoted lines
> "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

Previous: Junio C Hamano
Message 3 of 3 in “Static Linking git for HPE NonStop”
  1. Randall S. BeckerJun 26, 2020
  2. Junio C HamanoJun 26, 2020
  3. Randall S. BeckerJun 26, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.