CARGO trouble appeared from 2.54.0 to 2.55.0

CARGO trouble appeared from 2.54.0 to 2.55.0

[Kurt Mielke]

Hi


I had a clean alma10 and wanted the newest git BUT building fails:

make

....

     CC version.o
     AR libgit.a
     CARGO target/release/libgitcore.a
/bin/sh: line 1: cargo: command not found
make: *** [Makefile:3021: target/release/libgitcore.a] Error 127

I got 2.54.0 and it compiled just fine

I found out CARGO is rust related

Changing make command to

make NO_RUST=1

And I got my 2.55.0 version, but allow me to suggest it again is the default

II have no caommands in path beginning with the letters 'rus'

Thank you in advance

Kirt Mielke

Re: CARGO trouble appeared from 2.54.0 to 2.55.0

[Ben Knoble]

> Le 4 juil. 2026 à 20:23, Kurt Mielke <scr@lyn.dk> a écrit :
> 
> Hi
> 
> 
> I had a clean alma10 and wanted the newest git BUT building fails:
> 
> make
> 
> ....
> 
>     CC version.o
>     AR libgit.a
>     CARGO target/release/libgitcore.a
> /bin/sh: line 1: cargo: command not found
> make: *** [Makefile:3021: target/release/libgitcore.a] Error 127
> 
> I got 2.54.0 and it compiled just fine
> 
> I found out CARGO is rust related

Git’s source code has included some optional Rust components for a few releases now. Rust is planned to be a requirement for 3.0 (IIUC), but I don’t have any recollection of the proposed timeline. [There was also some discussion of delaying the Rust mandate timeline for platforms which currently lack support?]

> Changing make command to
> 
> make NO_RUST=1
> 
> And I got my 2.55.0 version, but allow me to suggest it again is the default

2.55 is the first version to flip the default to « build with Rust », but it remains optional as you’ve discovered. 

> II have no caommands in path beginning with the letters 'rus'
> 
> Thank you in advance
> 
> Kirt Mielke

Searching the internet shows Alma has packages for Rust, which you should be able to install if you want to compile with the Rust components. 

Re* CARGO trouble appeared from 2.54.0 to 2.55.0

[Junio C Hamano]

Ben Knoble <ben.knoble@gmail.com> writes:

> Git’s source code has included some optional Rust components for
> a few releases now. Rust is planned to be a requirement for 3.0
> (IIUC), but I don’t have any recollection of the proposed
> timeline. [There was also some discussion of delaying the Rust
> mandate timeline for platforms which currently lack support?]
> ...
> 2.55 is the first version to flip the default to « build with Rust
> », but it remains optional as you’ve discovered.
> ...
> Searching the internet shows Alma has packages for Rust, which you
> should be able to install if you want to compile with the Rust
> components.

As you said above, what was reported is totally expected (I
understand that 2.55 built properly for the OP with "make
NO_RUST=NoThanks" set).

I do not know why nobody complained, but we have been carrying this
incomplete sentence in the release notes forever X-<.

 Documentation/RelNotes/2.55.0.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git c/Documentation/RelNotes/2.55.0.adoc w/Documentation/RelNotes/2.55.0.adoc
index f5643534dc..696ad15c1e 100644
--- c/Documentation/RelNotes/2.55.0.adoc
+++ w/Documentation/RelNotes/2.55.0.adoc
@@ -85,8 +85,8 @@ Performance, Internal Implementation, Development Support etc.
  * Promisor remote handling has been refactored and fixed in
    preparation for auto-configuration of advertised remotes.
 
- * Rust support is enabled by default (but still allows opting out) in
-   some future version of Git.
+ * Rust support is enabled by default (but still allows opting out); in
+   some future version of Git, this will become mandatory.
 
  * Preparation of the xdiff/ codebase to work with Rust.