Re: rust update proposal

[Taylor R Campbell <campbell+netbsd-tech-pkg%mumble.net@localhost>]

> Date: Sun, 7 Jul 2024 11:37:22 +0000
> From: nia <nia%NetBSD.org@localhost>
> 
> On Sun, Jul 07, 2024 at 07:33:32AM -0400, Greg Troxel wrote:
> > nia <nia%NetBSD.org@localhost> writes:
> > 
> > There have been failures to build on armv7, which have felt to me like
> > not having the required gigabytes of ram, while rust-bin-x has been ok.
> 
> The build host is aarch64. Do you mean address space?
> 
> Both "exit status 101":
> 
> http://victory.netbsd.org/pkgsrc/packages/reports/2024Q2/evbarm7-10.0/20240705.0101/rust-1.76.0nb3/build.log

This one looks like some confusion around rust's libcurl wrapper:

error[E0463]: can't find crate for `curl`
 --> /pbulk/work/lang/rust/work/rustc-1.76.0-src/vendor/gix-transport/src/client/blocking_io/http/curl/remote.rs:9:5
  |
9 | use curl::easy::{Auth, Easy2};
  |     ^^^^ can't find crate

> http://victory.netbsd.org/pkgsrc/packages/reports/2024Q2/i386-10.0/20240705.1854/rust-1.76.0nb3/build.log

This one is a SIGSEGV in Rust:

rustc exited with signal: 11 (SIGSEGV)

It could be reaching some memory limit while linking `rustc-main'.
But since it's running on an amd64 host, it wouldn't be out of RAM.
So I don't know what's going on here.

Is there a way to make it try to print a stack trace in this case?