Re: lang/rust does not build on aarch64

Adrian Murphy <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>

> On 27 Jun 2021, at 7:37 pm, J P <[email protected]> wrote:
> 
> Hi,
> it seems rust does not build on aarch64:
> ===>  Building for rust-1.52.1
> rustup not detected: [Errno 2] No such file or directory: 'rustc'
> falling back to auto-detect
> running: /wrkdirs/usr/ports/lang/rust/work/bootstrap/bin/cargo build
> --manifest-path
> /wrkdirs/usr/ports/lang/rust/work/rustc-1.52.1-src/src/bootstrap/Cargo.toml
> --verbose --frozen
> Traceback (most recent call last):
>  File "x.py", line 27, in <module>
>    bootstrap.main()
>  File
> "/wrkdirs/usr/ports/lang/rust/work/rustc-1.52.1-src/src/bootstrap/bootstrap.py",
> line 1175, in main
>    bootstrap(help_triggered)
>  File
> "/wrkdirs/usr/ports/lang/rust/work/rustc-1.52.1-src/src/bootstrap/bootstrap.py",
> line 1148, in bootstrap
>    build.build_bootstrap()
>  File
> "/wrkdirs/usr/ports/lang/rust/work/rustc-1.52.1-src/src/bootstrap/bootstrap.py",
> line 900, in build_bootstrap
>    run(args, env=env, verbose=self.verbose)
>  File
> "/wrkdirs/usr/ports/lang/rust/work/rustc-1.52.1-src/src/bootstrap/bootstrap.py",
> line 153, in run
>    raise RuntimeError(err)
> RuntimeError: failed to run:
> /wrkdirs/usr/ports/lang/rust/work/bootstrap/bin/cargo build --manifest-path
> /wrkdirs/usr/ports/lang/rust/work/rustc-1.52.1-src/src/bootstrap/Cargo.toml
> --verbose --frozen
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/lang/rust
> 
> Is this known?

Is there a chance you ran out of memory?

I just had the same problem (I think) on an amd64 vm with 512MB ram and 1GB swap:

Jun 28 16:32:29 Menoetius kernel: swp_pager_getswapspace(11): failed
Jun 28 16:32:36 Menoetius kernel: pid 57952 (rustc), jid 0, uid 0, was killed: out of swap space

I progressed by giving it more ram.

Adrian 

> 
> Thank you.
> 
> BR,
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.