Skip to content

Conversation

@alvaro-cuesta
Copy link
Contributor

clang++ in MacOS Tahoe 26.0.1 fails with:

clang++: error: unknown argument: '-fexperimental-new-pass-manager'

This is due to clang >= 16 no longer supporting that flag.

Bumping Fairy-Stockfish submodule fixes the issue.

`clang++` fails with:

```
clang++: error: unknown argument: '-fexperimental-new-pass-manager'
```

Bumping Fairy-Stockfish submodule fixes the issue.
Copy link
Contributor Author

@alvaro-cuesta alvaro-cuesta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bumped Fairy-Stockfish to latest master but not sure what the update policy is or whether this could be a breaking change.

This is the minimum Fairy-Stockfish commit that would fix the issue: fairy-stockfish/Fairy-Stockfish@052dce6

path: fishnet-x86_64-apple-darwin
macos-aarch64:
runs-on: macos-13
runs-on: macos-26
Copy link
Contributor Author

@alvaro-cuesta alvaro-cuesta Oct 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added this to PR so we can consider the potential change. This would've caught the issue in CI.

The Apple Silicon build is currently running on macos-13 which is (1) Intel and (2) soon to be deprecated in a month. Is there any reason Apple Silicon was built on an Intel runner?

Changed to macos-26 just because it's the latest (and matches the environment where I found this issue!) but it's currently marked as "public preview" in GH docs. It should still be a good idea to update this at least to macos-14 due to the deprecation (macos-15 being the latest non-preview runner) and to build natively on Apple Silicon. macos-15 is also the minimum runner that has Clang 16 which would have caught this issue in CI.


Also note that the macos-x86-64 job is also using macos-13 and should probably be updated to macos-15-intel (which will also be deprecated in GH by Aug 2027) or cross-compile from an Apple Silicon runner.


Additionally: right below these lines there's...

CXXFLAGS: -target arm64-apple-macos11

I guess it was there because it was cross-compiling from Intel to Apple Silicon, but I still didn't touch it because that 11 makes me think there are breaking changes for binaries built targetting different MacOS versions?

Also note that the macos-x86-64 job is not specifying any CXXFLAGS so it might need a change to keep the target stable if macos-13 runner is changed.

@alvaro-cuesta alvaro-cuesta marked this pull request as ready for review October 9, 2025 16:04
@niklasf
Copy link
Member

niklasf commented Oct 12, 2025

I think the binaries for Windows and MacOS don't end up being fully static. So the strategy so far was just to use the oldest still available build environment, for maximum compatibility.

We can and should update Fairy-Stockfish.

@niklasf
Copy link
Member

niklasf commented Oct 23, 2025

Cherry-picked the submodule bump for now.

@niklasf niklasf closed this Oct 23, 2025
@alvaro-cuesta
Copy link
Contributor Author

@niklasf apologies for not following up, been pretty busy lately. Thanks for the bump.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants