Compilation failure on macOS Sequoia 15.5

[tomyedwab]

Summary

When running cargo run to build on my MacBook M2 Pro (2023) I get a compilation error. I followed the instructions on the "Building Zed for macOS" page.

Description

Steps to reproduce:

1. clone repo
2. xcode-select --install
3. sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
4. sudo xcodebuild -license accept
5. cargo run

Expected Behavior: Build succeeds.
Actual Behavior: Build fails halfway through with a large amount of errors.

I searched for the error text and did not find specific guidance on what this means or how to resolve it. I saw references to an -arch parameter but I do not see how that fits into the build process.

I can also elicit the same errors by running this command (not sure if it is correct):

xcrun -sdk macosx metal -o temp.ir -c crates/gpui/src/platform/mac/shaders.metal

error log

...
cargo:rerun-if-changed=./src/platform/mac/shaders.metal

  --- stderr
  metal shader compilation failed:
  In file included from ./src/platform/mac/shaders.metal:2:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/simd.h:22:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/vector.h:43:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/vector_types.h:92:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/base.h:37:
  /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/TargetConditionals.h:353:14: error: unrecognized arch using compiler with __is_target_arch support
              #error unrecognized arch using compiler with __is_target_arch support
               ^
  In file included from ./src/platform/mac/shaders.metal:2:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/simd.h:22:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/vector.h:43:
  /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/vector_types.h:129:54: error: typedef redefinition with different types ('char __attribute__((ext_vector_type(8)))' (vector of 8 'char' values) vs 'char8' (aka '__Reserved_Name__Do_not_use_char8'))
  typedef __attribute__((__ext_vector_type__(8))) char simd_char8;
                                                       ^
  /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/metal/32023/lib/clang/32023.620/include/metal/metal_extended_vector:268:15: note: previous definition is here
  typedef char8 simd_char8;
                ^
  In file included from ./src/platform/mac/shaders.metal:2:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/simd.h:22:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/vector.h:43:
  /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/simd/vector_types.h:137:55: error: typedef redefinition with different types ('char __attribute__((ext_vector_type(16)))' (vector of 16 'char' values) vs 'char16' (aka '__Reserved_Name__Do_not_use_char16'))
  typedef __attribute__((__ext_vector_type__(16))) char simd_char16;
                                                        ^
  /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/metal/32023/lib/clang/32023.620/include/metal/metal_extended_vector:269:16: note: previous definition is here
  typedef char16 simd_char16;
                 ^
(lots more below)

Zed Version and System Specs

The version of the code I am trying to build is commit f9f4be1.

[sukhmel]

Same here with macOS 15.7.1 on M1 Max

It looks like removing #include <simd/simd.h> in https://github.com/zed-industries/zed/blob/main/crates/gpui/src/platform/mac/shaders.metal fixes the build, so maybe there's SDK version issue where some versions needed it, and now there is a conflict? I'm yet to check if what is built that way works correctly if at all.

Upd: it does work, if there's a way to check for correctness other than simply running the app, I could run those too