Kirill A. Korinsky

@evanmiller I doubt that -latomic makes any harm on clang ;)

@evanmiller indeed. Anyway, I'd love to point here one more gcc bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94649

Just tested with GCC 12.1.0 => an issue still here :(

This is clear a bug inside GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 I not sure how to fix it, because clang hasn't got `-latomic` which is default compiler on modern macOS.

Just for records. An easy hack to make gcc works very well is adding `cargo:rustc-link-lib=atomic` to `script-overrides/stable-1.54.0-macos/build_libc.txt`

I'm using local root: 3ec8cd8b1a3431124d278baefc8d0e34dc69b930 and build fails on aarch64 with macOS 12 as: ``` > /Users/catap/src/mrustc/bin/mrustc rustc-1.39.0-src/vendor/libc/build.rs --crate-name build --crate-type bin -o output-1.39.0/build_libc-0_2_62_Hd_run -L output-1.39.0 -g --cfg feature=rustc-dep-of-std --cfg...

@bjorn3 but `1.54.0` should work ;) Here it has some quite deep issue.

@bjorn3 yes, but `1.54.0` is failed on something new at the first step of compiling which seems like a bug inside `mrustc`.

@thepowersgang I just tried a7eab91b002755bfa4b8065212207b8230cd84ec as local root and it crashed as: ``` bin/minicargo rustc-1.54.0-src/library/std --vendor-dir rustc-1.54.0-src/vendor --script-overrides script-overrides/stable-1.54.0-macos/ --output-dir output-1.54.0/ --manifest-overrides rustc-1.54.0-overrides.toml > /Users/catap/src/mrustc/bin/mrustc -Z print-cfgs (0/13) BUILDING core...

@thepowersgang I've just tested 2c4f89f87692f27246d1bc1e42c8d43df8514a71 on aarch64 and the issue still here on 1.54.0. Shall I create a new issue for 1.54.0?