macOS build failure: "archive member '/' not a mach-o file" during linking · Issue #20806 · iree-org/iree · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Report: Build Failure on macOS — "archive member '/' not a mach-o file"
Description
While building IREE on macOS using Clang, the build fails during linking with errors indicating that certain .a archive members are not Mach-O files. This issue appears during the final stages of linking and affects multiple static libraries.
🧪 Steps to Reproduce
First, clone the IREE repository:
git clone https://github.com/openxla/iree.git
cd iree
Then run the following commands to build IREE on macOS:
archive member '/' not a mach-o file in '/Users/compile_sanatan/ai_asm/iree-build/runtime/src/iree/io/libiree_io_scope_map.a'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
This repeats for multiple .a files in the build directory.
Bug Report: Build Failure on macOS — "archive member '/' not a mach-o file"
Description
While building IREE on macOS using Clang, the build fails during linking with errors indicating that certain
.a
archive members are not Mach-O files. This issue appears during the final stages of linking and affects multiple static libraries.🧪 Steps to Reproduce
First, clone the IREE repository:
git clone https://github.com/openxla/iree.git cd iree
Then run the following commands to build IREE on macOS:
cmake -G Ninja -B ../iree-build/ -S . \ -DCMAKE_BUILD_TYPE=RelWithDebInfo \ -DIREE_ENABLE_ASSERTIONS=ON \ -DCMAKE_C_COMPILER=clang \ -DCMAKE_CXX_COMPILER=clang++ \ -DIREE_ENABLE_LLD=ON
Then run:
💥 Actual Behavior
The build fails with multiple errors like:
This repeats for multiple
.a
files in the build directory.Attached the buildlog
build.log
The text was updated successfully, but these errors were encountered: