Saleem Abdulrasool

> ``` > :0: warning: using (deprecated) legacy driver, Swift installation does not contain swift-driver at: 'T:\5\bin\swift-driver-new.exe' > ``` > > Is that expected @compnerd? Yes, this is expected. We...

> @compnerd is there a good reason for this? It seems like it's causing some tests to behave differently only in Windows builds. Windows doesn't really do symlinks and the...

@benlangmuir yes, that would work on Windows as well. `-Xcc -I${env:SDKROOT}\usr\include` or `-Xcc %SDKROOT%\usr\include` (depending on the shell) should work I believe.

It seems that the error message that you are trying to search for might be one of: ``` C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.41.34120\include\type_traits:131:5: error: static assertion failed: Calling declval is ill-formed,...

I think that was recently introduced in 17.11.0. A temporary workaround might be to use 17.10.0 (though we will need to figure out what is going on here).

I think that this might be a bug in the older clang that we use for bootstrapping. It seems to work with the newer compiler. However, that uncovers another bug...

No, not currently; we build the compiler against the windows system libraries and compilers. The problem is that the SwiftCompilerSources is Swift code which falls back to the integrated clang.

@hjyamauchi we cannot pin the toolchain to 6.0 as the 5.10 toolchain is the agreed upon bootstrap toolchain for the project.

Well, I'd rather not pin the VS version for main - that needs to be fixed.

The failure has been fixed and we are currently using 17.14, going to close this for now.