From: Andy Koppe <andy.koppe@gmail.com>
To: git@vger.kernel.org
Cc: "Patrick Steinhardt " <ps@pks.im>,
"brian m . carlson " <sandals@crustytoothpaste.net>,
"Shardul Natu " <snatu@google.com>,
"Andy Koppe" <andy.koppe@gmail.com>
Subject: [PATCH] Makefile: pin cargo --target-dir to ./target
Date: Sun, 18 Oct 2026 21:53:05 +0100 [thread overview]
Message-ID: <20261018205305.2634339-1-andy.koppe@gmail.com> (raw)
The Makefile assumes that cargo places build artifacts under ./target.
That assumption breaks if the user has a custom target dir setting, e.g.
in their ~/.cargo/config.toml file or in the CARGO_TARGET_DIR env var.
This results in a link error due to failing to find the gitcore library
built with cargo.
To fix this, pass '--target-dir target' to the cargo commands that build
gitcore. Add it directly to the recipes rather than to CARGO_ARGS, so
that it isn't lost if CARGO_ARGS is overridden.
Leave the contrib/libgit-{sys,rs} targets alone, as nothing depends on
the location of their build output.
The Meson build of gitcore already passes --target-dir explicitly.
Signed-off-by: Andy Koppe <andy.koppe@gmail.com>
---
Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index c649c93c51..aea99a3639 100644
--- a/Makefile
+++ b/Makefile
@@ -3039,7 +3039,7 @@ $(LIB_FILE): $(LIB_OBJS)
ifndef NO_RUST
ifeq ($(RUST_TARGETS),)
$(RUST_LIB): Cargo.toml $(RUST_SOURCES) $(LIB_FILE)
- $(QUIET_CARGO)cargo build $(CARGO_ARGS)
+ $(QUIET_CARGO)cargo build $(CARGO_ARGS) --target-dir target
else
ifneq ($(words $(RUST_TARGETS)),1)
ifneq ($(uname_S),Darwin)
@@ -3049,7 +3049,7 @@ endif
RUST_MEMBER_LIBS = $(foreach target,$(RUST_TARGETS),target/$(target)/$(RUST_BUILD_CONFIG)/$(RUST_LIB_NAME))
$(RUST_MEMBER_LIBS): target/%/$(RUST_BUILD_CONFIG)/$(RUST_LIB_NAME): Cargo.toml $(RUST_SOURCES) $(LIB_FILE)
- $(QUIET_CARGO)cargo build $(CARGO_ARGS) --target $*
+ $(QUIET_CARGO)cargo build $(CARGO_ARGS) --target-dir target --target $*
$(RUST_LIB): $(RUST_MEMBER_LIBS)
$(call mkdir_p_parent_template)
--
2.56.0
next reply other threads:[~2026-10-18 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 20:53 Andy Koppe [this message]
2026-10-19 6:45 ` [PATCH] Makefile: pin cargo --target-dir to ./target Patrick Steinhardt
2026-10-19 16:07 ` Junio C Hamano
2026-10-19 19:43 ` Andy Koppe
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=20261018205305.2634339-1-andy.koppe@gmail.com \
--to=andy.koppe@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=sandals@crustytoothpaste.net \
--cc=snatu@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.