rust is the new bit rot?

[raf]

On Sat, Jul 27, 2024 at 04:45:07AM -0700, "René J.V. Bertin" <rjvbertin at gmail.com> wrote:

> Hi,
> 
> A bit of a rant.
> 
> A little over a year ago I wrote a rustup PortGroup that allowed me to build ports with a build dependency on rust using an on-the-fly install of the necessary toolchain via rustup. That worked like a charm, and it fact it still does on Linux. Annoyingly builds that succeeded a year ago now fail on Mac (under 10.9) with a SEGV under fseek64 or a similar syscall, without any incrimination of an updated dependency in MacPorts. Several hours of effort yesterday to update get it to work again  were in vain. I didn't manage to build the current rust from source, and the binary package for darwin13  installs a rustc compiler that crashes with pointer-not-freed aborts when I try to build rustup from source. The backtrace in the crash reporter is useless of course.
> I can download the official rustup-init executable which runs after relinking it with the legacy-support wrapper for libSystem but it downloads a toolchain that's crippled too.
> 
> Comments and Portfile code suggest that rust should work on darwin13 but are there people who have actually tested this? I see there are binary librsvg packages for darwin10 even, but the build bots are not entirely representative for production/user systems that have a myriad of (theoretically unrelated) ports installed.
> 
> Maybe I need to check my legacy-support port?
> 
> R.

I've recently tried to install ripgrep (which is written in rust)
on 10.6 and 10.4 and it failed. I think it was cargo that failed.
I haven't reported it yet.

cheers,
raf