Re: Rust amd64 build failure.

[Mike Pumford <mpumford%mudcovered.org.uk@localhost>]

On 11/04/2023 21:01, Havard Eidnes wrote:

> Well, what can I say, it builds for me -- this is natively on
> NetBSD/amd64 9.3.  My build log doesn't contain the
> "pre-installed rustc not detected" message -- it starts the build
> proper with:
>
> ===> Building for rust-1.68.2
> detected default triple x86_64-unknown-netbsd from pre-installed rustc
> Building rustbuild
> running: /usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/cargo build --manifest-path /usr/pkgsrc/lang/rust/work/rustc-1.68.2-src/src/bootstrap/Cargo.toml --frozen
Doesn't that mean you already have a rust setup installed on the system. 
That's a circular dependency that's never going to work for anyone 
starting fresh (which is what my chroot does).

Since I sent my e-mail I've reproduced the same failure in a 10-BETA 
chroot so its got nothing to do with libkver.

Looking back at my last successful build which was of rust 1.66.1 The 
logs show:

==> Building for rust-1.66.1
pre-installed rustc not detected: [Errno 2] No such file or directory: 
'rustc'
falling back to auto-detect
Building rustbuild
running: /comp/obj/pkgsrc/lang/rust/work/rust-bootstrap/bin/cargo build 
--manifest-path 
/comp/obj/pkgsrc/lang/rust/work/rustc-1.66.1-src/src/bootstrap/Cargo.toml 
--frozen
   Compiling libc v0.2.126
   Compiling proc-macro2 v1.0.46
   Compiling cfg-if v1.0.0

So the lack of pre-installed rust is not a problem.

Digging a bit deeper into the failing log I spotted:

thread 'main' panicked at 'unexpected error from isatty: 45', 
/cargo/registry/src/github.com-1ecc6299db9ec823/rustix-0.36.3/src/backend/libc/termios/syscalls.rs:141:20

errno 45 is EOPNOTSUPP (operation not supported)

Could the new rust be assuming that its running on a TTY device. This 
isn't something that a compiler should be assuming.

Mike