Jeremy Kun

This error occurs when you don't have a full xcode installation on your machine. For whatever reason, the bazel infrastructure for MacOS requires this. The command-line tools alone do not...

Cf. https://github.com/bazelbuild/bazel/issues/25728. I might be able to find a workaround

As an experiment, you could try patching this PR and rebuilding: https://github.com/google/heir/pull/2181

> `invalid linker name in argument '-fuse-ld=ld64.lld:'` The trailing colon looks like a typo in a `.bazelrc`, maybe on your system (could be in `$HOME/.bazelrc`?). In the checked-in repo, for...

> Hello, I've installed Xcode fully and tried out both the PR and the newest main content, but it both shows error about Xcode, this is the error log. Thank...

Reading a few other places, you may also find the command `bazel fetch --configure --force` useful, which re-runs the parts of the compiler toolchain setup that detects external dependencies (like...

LLVM should not be required as a system dependency, since we build it from scratch in the project. If it is for some reason, that'd be a bug for me...

@Kidebazelno I suspect it's using a homebrew-installed clang instead of apple clang, despite your shell's `clang` correctly pointing to apple clang. Can you try pasting the output of `bazel cquery...

I would indeed try removing lld. I had previously tested my build on xcode 16.4, but I am currently upgrading to 26.1 so I can test that newer version.

I was able to build with xcode 26.1, though I did learn that, because I have rust installed on my machine, it comes with `llvm 20` ``` $ brew info...