Build script binaries crash with "dyld: malformed mach-o image: missing LC_DYSYMTAB" on macOS 10.15 when "strip = true"

[RandomInsano]

It seems that on macOS 10.15, when enabling symbol stripping in Cargo.toml with strip = true the build scripts fail to execute with the following:

error: failed to run custom build command for `libc v0.2.152`

Caused by:
  process didn't exit successfully: `/Users/me/Documents/Code/rust/others/repro/target/problem/build/libc-0c18316fbaf15a0a/build-script-build` (signal: 6, SIGABRT: process abort signal)
  --- stderr
  dyld: malformed mach-o image: missing LC_DYSYMTAB

Here's the minimal reproducible test case

cargo new --bin repro
cd repro
cat >> Cargo.toml <<EOF
[profile.problem]
inherits = "release"
strip = true
EOF
cargo add libc
cargo build --profile problem # Fails
cargo build --release # Works fine

I expected to see this happen: I expected proper compilation and execution of stripped binaries.

Instead, this happened: It dun when kaboom.

Meta

I tested these versions:

$ cargo +nightly --version --verbose
cargo 1.77.0-nightly (2ce45605d 2024-01-04)
release: 1.77.0-nightly
commit-hash: 2ce45605d9db521b5fd6c1211ce8de6055fdb24e
commit-date: 2024-01-04
host: x86_64-apple-darwin
libgit2: 1.7.1 (sys:0.18.1 vendored)
libcurl: 7.64.1 (sys:0.4.70+curl-8.5.0 system ssl:(SecureTransport) LibreSSL/2.8.3)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Mac OS 10.15.7 [64-bit]

$ cargo +stable --version --verbose
cargo 1.75.0 (1d8b05cdd 2023-11-20)
release: 1.75.0
commit-hash: 1d8b05cdd1287c64467306cf3ca2c8ac60c11eb0
commit-date: 2023-11-20
host: x86_64-apple-darwin
libgit2: 1.7.1 (sys:0.18.1 vendored)
libcurl: 7.64.1 (sys:0.4.68+curl-8.4.0 system ssl:(SecureTransport) LibreSSL/2.8.3)
ssl: OpenSSL 1.1.1u  30 May 2023
os: Mac OS 10.15.7 [64-bit]

Backtrace wasn't helpful as this is a lower-level problem.

[RandomInsano]

Some additional detail: This does not occur on an M1 Mac running macOS 12.7.2.

I tested with version 1.60.0, and it still occurs there. Using the advice from !3480 actually doesn't have problems:

$ RUSTFLAGS='-C link-arg=-s' cargo build --release
   Compiling libc v0.2.152
   Compiling repro v0.1.0 (/Users/me/Documents/Code/rust/others/repro)
    Finished release [optimized] target(s) in 2.39s

Considering the strip feature was introduced in 1.59.0 and I believe I was developing an application that used that feature on this version of Rust, there may be something else wrong with my setup... Does Rust call out to anything else on macOS that may have been updated?

[RandomInsano]

Ah, last thing for the day but it doesn't look like it's a Rust problem specifically:

$ target/debug/repro 
Hello, world!
$ strip target/debug/repro 
$ target/debug/repro 
dyld: malformed mach-o image: missing LC_DYSYMTAB
Abort trap: 6

$ strip --version
GNU strip (GNU Binutils) 2.35.1
Copyright (C) 2020 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.

$ which strip
/usr/local/opt/binutils/bin/strip

Looks like this adventure was because I had binutils installed from Homebrew. Sorry for the noise! Hopefully this can help someone else.

[workingjubilee]

should be fixed by #131405

[RandomInsano]

Thanks much!