232606 2021-11-01 22:48:23 -0700 Compile failure with macOS 11.6.1 + XCode 13.1: …/PAL.build/Release/PAL.build/Objects-normal/x86_64/OutputContext.o pal/avfoundation/OutputContext.mm normal x86_64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler 2021-12-01 22:55:10 -0800 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 226235 https://bugs.webkit.org/show_bug.cgi?id=226235 P2 Normal --- 1 mike webkit-unassigned beidson darin oldest_to_newest 1811035 0 mike 2021-11-01 22:48:23 -0700 Clean build on macOS 11.6.1 with XCode 13.1, I hit this: > The following build commands failed: CompileC /opt/webkit/WebKitBuild/PAL.build/Release/PAL.build/Objects-normal/x86_64/OutputContext.o pal/avfoundation/OutputContext.mm normal x86_64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler (1 failure) 1812610 1 gsnedders 2021-11-08 08:08:48 -0800 as mentioned on Slack, this is just 226235 again *** This bug has been marked as a duplicate of bug 226235 *** 1812653 2 ap 2021-11-08 09:37:17 -0800 This can (and ideally, should) be fixed separately from bug 226235. Warning about a poorly supported configuration would be good, but failing to build with latest Xcode is not really OK, whether we can actively support this scenario at this time, or not. 1815963 3 darin 2021-11-17 09:08:21 -0800 I am a little puzzled about whether this is an issue with mismatching SDKs or something else. 1819578 4 beidson 2021-12-01 22:55:10 -0800 (In reply to Darin Adler from comment #3) > I am a little puzzled about whether this is an issue with mismatching SDKs > or something else. I ran into this form - https://bugs.webkit.org/show_bug.cgi?id=232454 - on my personal machine running macOS 11.6, but with Xcode 13. Steps to reproduce: 1 - Running macOS 11, Install Xcode 13 and xcode-select it 2 - `build-webkit` <---- fails Alternative steps to reproduce: 1 - Running macOS 11, Install Xcode 13 and xcode-select it 2 - Open WebKit.xcworkspace 3 - Build the entire WebKit target <--- fails. Doing the above steps are - of course - entirely reasonable things to do. In my case, at least, the problem was definitely with the source code as checked in to the WebKit open source project, and I'm fixing it. I'm sure what other forms are manifesting but... "Running a version of macOS that still supports trunk WebKit... and then installing the latest dev tools" is probably something that should work.