https://bugzilla.suse.com/show_bug.cgi?id=1222269 Bug ID: 1222269 Summary: LLVM run OOM while building typst for armv6/7 with 24G of RAM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs@suse.de Reporter: guillaume.gardet@arm.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- LLVM run OOM while building typst for armv6/7 with 24G of RAM while aarch64 requires 11.8G of RAM ********** [ 173s] Compiling typst-ide v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/crates/typst-ide) [ 429s] Compiling typst-fuzz v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/tests/fuzz) [ 658s] LLVM ERROR: out of memory [ 658s] Allocation failed [ 658s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 658s] called `Option::unwrap()` on a `None` value [ 658s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 658s] error: could not compile `typst-docs` (bin "typst-docs") [ 658s] warning: build failed, waiting for other jobs to finish... [ 663s] LLVM ERROR: out of memory [ 663s] Allocation failed [ 664s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 664s] called `Option::unwrap()` on a `None` value [ 664s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 664s] error: could not compile `typst-fuzz` (bin "compile") [ 694s] LLVM ERROR: out of memory [ 694s] Allocation failed [ 694s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 694s] called `Option::unwrap()` on a `None` value [ 694s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 694s] error: could not compile `typst-cli` (bin "typst") [ 694s] error: Bad exit status from /var/tmp/rpm-tmp.R2PFPX (%build) ********** See: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/typst... -- You are receiving this mail because: You are on the CC list for the bug.