From: <rsbecker@nexbridge.com>
To: <rsbecker@nexbridge.com>, <git@vger.kernel.org>
Subject: RE: Need help on building git with static libz.a
Date: Tue, 29 Aug 2023 13:23:44 -0400 [thread overview]
Message-ID: <07af01d9da9d$9355e1a0$ba01a4e0$@nexbridge.com> (raw)
In-Reply-To: <079601d9da8c$8768cfd0$963a6f70$@nexbridge.com>
On Tuesday, August 29, 2023 11:22 AM, I wrote:
>To: git@vger.kernel.org
>Sorry if I seem clueless on this within the git make infrastructure, but
someone set up
>my new build environment with an incompatible libz.so that I cannot seem to
bypass.
>How can I link git using libz.a instead?
Simple solution is to put the full path to libz.a before any -L in LDFLAGS.
prev parent reply other threads:[~2023-08-29 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:21 Need help on building git with static libz.a rsbecker
2023-08-29 17:23 ` rsbecker [this message]
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='07af01d9da9d$9355e1a0$ba01a4e0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
/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).