Git development
 help / color / mirror / Atom feed
From: Ben Knoble <ben.knoble@gmail.com>
To: Kurt Mielke <scr@lyn.dk>
Cc: git@vger.kernel.org
Subject: Re: CARGO trouble appeared from 2.54.0 to 2.55.0
Date: Sun, 5 Jul 2026 19:56:23 -0400	[thread overview]
Message-ID: <81CE676D-CBBD-44E9-8DD6-B34068E35769@gmail.com> (raw)
In-Reply-To: <bb2a925e-0b01-4e12-88ed-44deea0c90a1@lyn.dk>


> 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. 

  reply	other threads:[~2026-07-05 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05  0:21 CARGO trouble appeared from 2.54.0 to 2.55.0 Kurt Mielke
2026-07-05 23:56 ` Ben Knoble [this message]
2026-07-06 14:13   ` Re* " Junio C Hamano

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=81CE676D-CBBD-44E9-8DD6-B34068E35769@gmail.com \
    --to=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=scr@lyn.dk \
    /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