Has anyone had a successful Xcode build recently? After 2 sequential failures I took a glance at the job on ci.swift.org and it appears to have been failing for an indefinite amount of time. My arguments are utils/build-script --release-debuginfo --debug-swift --xcode
I was foolish enough not to copy the error before quitting the terminal, but I do remember it was pointing at something named SwiftNativeNSXXXBase. A repeated incremental build somehow skipped that and failed closer to the end with
The following build commands failed:
swift-macosx-x86_64/Debug/lib/swift/macosx/x86_64/libswiftCore.dylib normal x86_64
This probably doesn't help at all, so merely FYI. Please let me know if the team is aware of the build failing.
It actually was a clean build, and I currently have only one version of Xcode (the required one, of course), so I doubt --reconfigure will make any difference. I don't think it affects clean builds anyways, but I'll give it a go tonight, who knows.
I just did an update-checkout this morning (about 2 hours ago), so it should have built with all the latest changes. I'm using the latest Xcode from the Appstore. The actual build was done with utils/build-script --release-debuginfo --debug-swift --skip-build-benchmarks --skip-test-benchmarks --skip-ios --skip-tvos --xcode -c
I've had problems with the Xcode build that are solved by manually deleting the generated files from .gyb sources. This is obviously not an acceptable state of affairs, but no one's really looked into it.
This time deleting the generated files from .gyb (deleting all .swift files from the build directory) didn't work, but I will consider this possibility for the future, thank you. I tried repeating update-checkout and starting a clean build again, but it continues to fail with Build input file cannot be found: SwiftNativeNSXXXBase.mm right after finishing with llvm. From there an incremental build simply fails later on with the error in my OP. I am on macOS 10.14.1. The Xcode version is Xcode 10.1 (10B61) – the same one used by the ci bots. Couldn't the issue be related to the still failing build on ci? Is there any way to check out the console log? I wonder how Erik got a successful build though.
Yeah, I think this has been broken for a few days, I meant to file a bug but forgot and haven’t had tine to debug it myself, not sure if it’s a clang or cmake issue. In case you’re not aware, you can also use the -skip-build build script flag to generate an Xcode project for editing, jump to definition, etc. without actually building