It looks like this is happen during the build of the faster-fifo library, which is not part of the MAX code specifically, but seems to be a Python dependency.
I wonder if Xcode or Xcode Command Line Tools are installed correctly on this machine. You can see the system requirements for MAX here: MAX FAQ | Modular Docs
You can run this command to check for an Xcode installation:
xcode-select -p
If Xcode is not installed, you can install it from the Mac App Store. If you have Xcode installed but not the Xcode Command Line Tools, you can install them with:
I can’t reproduce this unfortunately! looks like a local toolchain issue as Josh said compiling the dependency which uses Cython. Could you try magic clean and then magic add --pypi Cython prior to running llama3?
We had some folks hit this on Tuesday too. faster-fifo is a C++ based python lib but doesn’t release binary wheels, only a source package, so it requires that you have a local compatible C++ toolchain (like from xcode) setup.
Updating xcode might help, but running on macos 11 it may be a challenge to get a compatible C++ toolchain and may still run into issues there. I recommend updating to macos 14 or 15.2 at least.
Good eye to see the toolchain was for macOS 11, I did not notice that @Zac! Our minimum requirements indicate MAX needs macOS 13 at least, so even if we get this to work, something might fail later on macOS 11.
I have MacOS Sequoia 15.1.1. I am not sure why the path has macOS-11.0.
I have the Xcode tools already
❯ xcode-select --install
xcode-select: note: Command line tools are already installed. Use "Software Update" in System Settings or the softwareupdate command line interface to install updates
It looks like there are updates to both the OS and Xcode cli, installing those now.
I have a C++ compiler installed
❯ c++ --version
Apple clang version 16.0.0 (clang-1600.0.26.4)
Target: arm64-apple-darwin24.1.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
I cannot add Cython, running magic add --pypi Cython fails with the same C++ compilation error.
I wonder if something is wrong with the SDK path, and Xcode is trying to use an older (11.0) SDK version. Can you try this command?
xcrun --show-sdk-path
That should display the SDK path. That path is likely a symlink. On my machine is is /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk. Then you can run this command, where the argument is the SDK path:
ls -al /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
My machine reports /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk ⇒ MacOSX15.1.sdk. I wonder if your path is pointing to the 11.0 SDK for some reason.
Thanks for checking! Is there any other part of that error message? I wonder if we can somehow see the actual error from the C++ compiler. Maybe it gets put in a log file somewhere.