From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.55.0-rc0
Date: Fri, 12 Jun 2026 21:56:37 -0400 [thread overview]
Message-ID: <06b101dcfad7$e2600b10$a7202130$@nexbridge.com> (raw)
In-Reply-To: <xmqqzf0zhjuq.fsf@gitster.g>
On June 12, 2026 11:14 AM, Junio C Hamano wrote:
> <rsbecker@nexbridge.com> writes:
>
> > On June 11, 2026 11:32 AM, Junio wrote:
> >> An early preview release Git v2.55.0-rc0 is now available for testing
> >> at the usual places. It is comprised of 397 non-merge commits since
> >> v2.54.0, contributed by
> >> 70 people, 22 of which are new faces [*].
> >
> > Cargo is not available everywhere. Build is not possible on NonStop.
> >
> > cargo build --release
> > /usr/coreutils/bin/bash: cargo: command not found
> > Makefile:3021: recipe for target 'target/release/libgitcore.a' failed
> > make: *** [target/release/libgitcore.a] Error 127
> >
> > Is there a way around this?
>
> I see this in the Makefile that you may or may not have read. Does it
work?
>
> # Define NO_RUST if you want to disable features and subsystems written in
Rust #
> from being compiled into Git. For now, Rust is still an optional feature
of # the build
> process. With Git 3.0 though, Rust will always be enabled.
Thanks. Adding NO_RUST=yes to the command line for make worked properly.
prev parent reply other threads:[~2026-06-13 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 15:32 [ANNOUNCE] Git v2.55.0-rc0 Junio C Hamano
2026-06-12 14:13 ` rsbecker
2026-06-12 15:03 ` rsbecker
2026-06-12 15:14 ` Junio C Hamano
2026-06-13 1:56 ` 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='06b101dcfad7$e2600b10$a7202130$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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