Re: cargo-c

[pin <voidpin%protonmail.com@localhost>]

On Wednesday, April 16th, 2025 at 2:25 PM, Greg Troxel <gdt%lexort.com@localhost> wrote:

> pin voidpin%protonmail.com@localhost writes:
> 
> > devel/cargo-c in pkgsrc is currently stuck at version 0.9.32
> > 
> > This version was added on 2024-05-05 and is the last version that builds with Rust-1.76.
> > For almost a year, I've been keeping wip/cargo-c up-to-date (currently version 0.10.12) and using it on all my builds.
> > 
> > I would like to import 0.10.12 into the main branch and probably deprecate Rust-1.76
> > 
> > Any reasons not to do this?
> > If so, how much longer should we wait?
> 
> 
> We have rust176 and rust (1.85.1).
> 
> As I understand it, vast amounts of things in rust depend on cargo-c, so
> this step would mean that unless a platform can run up-to-date rust, all
> rust programs will be BROKEN on thosee platforms. So...
> 
> Does not having up-to-date rust and new cargo-c (only) really imply
> that most rust programs will break?
> 
> What is the set of platforms that can run rust-1.76 and cannot (even
> with rust-bin) run the current version (1.85.1?)?

It's my understanding that cross-compiled rust-bin should work on all platforms.
Hence my question about the update, as I no longer see a reason to hold it back.
But, perhaps he@ can comment.
32bits ARM cannot natively build rust > 1.76


> What is the minimum rust version for new cargo-c?

1.84


> My take is that it's increasing less reasonable to hold things back for
> netbsd-9 as it's more than 5 years old*, but that we need to have a path
> for NetBSD 10 on earmv7hf-el with 1 GB of RAM (e.g. RPI2/3).

Please see answer to the first question.