Anyone unable to build on Mac?

[Esau Garcia]

OS: Sonoma 14.6.1

AMD x86_64

I'm trying to build chromium after making sure I have the xcode tools and chromium's depot_tools  but I consistently fall into the following error:
```

Error: failed in schedule out/Default/chrome: schedule out/Default/phony/chrome/chrome: schedule out/Default/phony/chrome/chrome_app: schedule out/Default/Chromium.app/Contents/Resources/af.lproj/InfoPlist.strings: schedule out/Default/gen/chrome/app_infoplist_strings/af.lproj/InfoPlist.strings: schedule out/Default/infoplist_strings_util: schedule out/Default/obj/chrome/tools/build/mac/infoplist_strings_util/infoplist_strings_util.o: schedule out/Default/obj/buildtools/third_party/libc++/MachO/DarwinBasic.pcm: schedule out/Default/obj/buildtools/third_party/libc++/_AvailabilityInternal/DarwinFoundation1.pcm: schedule /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk/usr/include/DarwinFoundation1.modulemap: "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk/usr/include/DarwinFoundation1.modulemap", needed by "obj/buildtoo

```

[Thomas Beverley]

I had this - I think an Xcode update fixed it

[zhengxianwei]

This is because the macOS SDK version required by your build does not match the version actually installed on your system. You can manually specify the SDK version — here’s an example:

```

# Build arguments go here.
# See "gn args <out_dir> --list" for available build arguments.

mac_sdk_path = "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX26.0.sdk"


is_debug = true
is_component_build = true
symbol_level = 2
use_jumbo_build = true
use_goma = false
enable_nacl = false
is_official_build = false
dcheck_always_on = true

```

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[ANDRI Business Authorized]

It looks like the issue comes from a mismatch between the macOS SDK version and what Chromium’s build configuration currently supports.

The log shows it’s trying to include:

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk/usr/include/DarwinFoundation1.modulemap however as of now, Chromium doesn’t officially support macOS 15 SDK (Sequoia) the build scripts and GN configuration are still tuned for macOS 14 (Sonoma) SDK. This is why you’re seeing the chain of “schedule” build errors — the build system can’t resolve or generate the expected .pcm modules from that newer SDK’s modulemap.

Fix options:

1. Install an older Xcode version that ships with the macOS 14.x SDK.

   • You can find older releases here: https://developer.apple.com/download/all/

   • Xcode 15.4 (includes macOS 14.5 SDK).

2. Point your build to that older SDK manually:

   export SDKROOT=/Applications/Xcode_15.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.5.sdk

   Then clean and rebuild:

   autoninja -C out/Default chrome

3. Alternatively, if you must stay on macOS 15 SDK, you’ll need to patch Chromium’s GN configuration or wait until the Chromium team officially updates SDK compatibility (this is in progress internally).

So in short. it’s not your setup or depot_tools issue, it’s that the latest SDK (15.2) is ahead of what Chromium’s build system recognizes.