Re: building rust with x.py from today's git ends in SIGSEGV

[ci4ic4 <ci4ic4%proton.me@localhost>]

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Mon, Jan 13, 2025 at 22:20, Greg A. Woods <[woods%planix.ca@localhost](mailto:On Mon, Jan 13, 2025 at 22:20, Greg A. Woods <<a href=)> wrote:

> Has anyone had any luck building a rust compiler from their repository
> using the default "x.py" method? (I don't want to build LLVM from
> source, so I'll use their binary if necessary.)
>
> Running "./x" (on a NetBSD/amd64 system) chewed away for a while and
> ended with what seemed to be a working "stage0" compiler.
>
> I then tried "./x build", and it chewed away for some more time, then
> ended with:
>
> Creating a sysroot for stage1 compiler (use `rustup toolchain link 'name' build/host/stage1`)
> Building stage1 library artifacts {alloc, core, panic_abort, panic_unwind, proc_macro, std, sysroot, test, unwind} (x86_64-unknown-netbsd)
> error: failed to run `rustc` to learn about target-specific information
>
> Caused by:
> process didn't exit successfully: `/work/woods/m-rust/build/bootstrap/debug/rustc /work/woods/m-rust/build/bootstrap/debug/rustc - --crate-name ___ --print=file-names -Csymbol-mangling-version=legacy '--check-cfg=cfg(feature,values(any()))' -Zunstable-options '--check-cfg=cfg(bootstrap)' -Zmacro-backtrace -Csplit-debuginfo=off -Cprefer-dynamic -Zinline-mir -Zinline-mir-preserve-debug -Zmir_strip_debuginfo=locals-in-tiny-functions -Clink-args=-Wl,-z,origin '-Clink-args=-Wl,-rpath,$ORIGIN/../lib' -Cembed-bitcode=yes -Cforce-frame-pointers=yes '-Zcrate-attr=doc(html_root_url="https://doc.rust-lang.org/nightly/";)' --target x86_64-unknown-netbsd --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 254)
> --- stderr
> rustc exited with signal: 11 (SIGSEGV) (core dumped)

I got exactly the same running x.py.

> Hmmm.... that seems unexpected! Especially for a procedure that would
> seem to just be printing some environment information.
>
> GDB doesn't seem to find any symbols in the bootstrap rustc (despite it
> being "not stripped") so the core file isn't of much use so far....

same here.

> BTW, does anyone know if there's any progress/movement on an alternative
> backend to LLVM for rust?
>
> --
> Greg A. Woods <gwoods%acm.org@localhost>
>
> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost>
> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>