Canop / Canop/bacon

Can't build on M3 MacPro with sold linker

Open
#173 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
3.4k
Forks
126
Avg merge
2d 1h
Merged PRs (30d)
7

Description

```
> $ cargo install --path .
Installing bacon v2.14.3-dev (/Users/fcoury/code/bacon)
Updating crates.io index
Compiling proc-macro2 v1.0.78
Compiling unicode-ident v1.0.12
Compiling libc v0.2.153
Compiling autocfg v1.1.0
Compiling thiserror v1.0.57
Compiling cfg-if v1.0.0
Compiling serde v1.0.197
Compiling parking_lot_core v0.9.9
Compiling memchr v2.7.1
Compiling crossbeam-utils v0.8.19
Compiling regex-syntax v0.8.2
Compiling once_cell v1.19.0
Compiling smallvec v1.13.1
Compiling scopeguard v1.2.0
Compiling tinyvec_macros v0.1.1
Compiling gix-trace v0.1.7
Compiling rayon-core v1.12.1
Compiling tinyvec v1.6.0
Compiling crc32fast v1.4.0
Compiling fastrand v2.0.1
Compiling adler v1.0.2
Compiling same-file v1.0.6
Compiling bitflags v2.4.2
Compiling either v1.10.0
Compiling walkdir v2.4.0
Compiling lock_api v0.4.11
Compiling aho-corasick v1.1.2
Compiling miniz_oxide v0.7.2
Compiling bytesize v1.3.0
error: failed to run custom build command for `thiserror v1.0.57`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/thiserror-5ab653d5974c1640/build-script-build` (signal: 10, SIGBUS: access to undefined memory)
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `rayon-core v1.12.1`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/rayon-core-2c5ae3065a5d199f/build-script-build` (signal: 10, SIGBUS: access to undefined memory)
error: failed to run custom build command for `serde v1.0.197`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/serde-32f36e526d05b2fa/build-script-build` (signal: 11, SIGSEGV: invalid memory reference)
error: failed to run custom build command for `parking_lot_core v0.9.9`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/parking_lot_core-4a7529d07e68ff4c/build-script-build` (signal: 10, SIGBUS: access to undefined memory)
error: failed to run custom build command for `crossbeam-utils v0.8.19`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/crossbeam-utils-eeed6c8973fa880e/build-script-build` (signal: 10, SIGBUS: access to undefined memory)
error: failed to run custom build command for `proc-macro2 v1.0.78`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/proc-macro2-296ff4b34021689d/build-script-build` (signal: 10, SIGBUS: access to undefined memory)
error: failed to run custom build command for `crc32fast v1.4.0`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/crc32fast-57edd767e203b1e3/build-script-build` (signal: 11, SIGSEGV: invalid memory reference)
error: failed to run custom build command for `libc v0.2.153`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/libc-7d3c3772beff9ff0/build-script-build` (signal: 10, SIGBUS: access to undefined memory)
error: failed to run custom build command for `lock_api v0.4.11`

Caused by:
process didn't exit successfully: `/Users/fcoury/code/bacon/target/release/build/lock_api-10916c91955e0afb/build-script-build` (signal: 10, SIGBUS: access to undefined memory)
error: failed to compile `bacon v2.14.3-dev (/Users/fcoury/code/bacon)`, intermediate artifacts can be found at `/Users/fcoury/code/bacon/target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `cargo install --path .` on the reported M3 MacPro environment. The output shows failures in custom build commands for thiserror, rayon-core, serde, parking_lot_core, crossbeam-utils, proc-macro2, crc32fast, libc, and lock_api; determine whether the build can complete without SIGBUS or SIGSEGV before defining the fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.