You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this exact issue will be fixed in tonight's snapshot, at least not able to reproduce it locally anymore thanks to c7557be. Nevertheless, there's a different issue with SwiftPM on macOS, which prevents it from working properly. I think it has something to be with how libPackageDescription.dylibthat belongs to SwiftPM is compiled. If you completely clean your .build directory (for any package, not just Tokamak) you get this error:
error: manifest parse error(s):
<unknown>
The breakage happens when the Package.swift manifest path is compiled, you can infer by passing the -v flag to swift build and checking where exactly the error occurs:
Note that I'm using 2020-06-13-a snapshot in the above output, that's the oldest snapshot where the issue is reproduced. 2020-06-12-a snapshot is working fine. I've also tried to compile the manifest file separately by 2020-06-13-a and 2020-06-12-a versions of the compiler, but using the same version of the libPackageDescription.dylib module from either 2020-06-13-a or 2020-06-12-a. Testing these different combinations, I think that the issues is caused by libPackageDescription.dylib that became broken in 2020-06-13-a and is still broken in the latest snapshots for both swiftwasm-release/5.3 and swiftwasm branches. Looking at file sizes, we can also see that something happened to the library that significantly changed its binary size starting with the 2020-06-13-a snapshot:
There don't seem to be any changes between 2020-06-12-a and 2020-06-13-a in the SwiftPM itself, I think something changed in the compiler that made it miscompile the library.
I'm going to research this further, need to investigate what exactly is different between those two compiler versions and how to fix it.
Build both host and target toolchains on CI
Both `libPackageDescription.dylib` and `swiftc` used to compile package manifests should come from the same toolchain for SwiftPM to work on macOS. This is resolved here by re-reverting the previous change #1024 to build both host and target toolchain in one go on CI. I'm wary of the disk space/time limit constraints, but I think those should be resolved separately when they appear, otherwise SwiftPM is completely broken on macOS currently. Resolves#1365.
I think this exact issue will be fixed in tonight's snapshot, at least not able to reproduce it locally anymore thanks to c7557be. Nevertheless, there's a different issue with SwiftPM on macOS, which prevents it from working properly. I think it has something to be with how
libPackageDescription.dylib
that belongs to SwiftPM is compiled. If you completely clean your.build
directory (for any package, not just Tokamak) you get this error:The breakage happens when the
Package.swift
manifest path is compiled, you can infer by passing the-v
flag toswift build
and checking where exactly the error occurs:Note that I'm using
2020-06-13-a
snapshot in the above output, that's the oldest snapshot where the issue is reproduced.2020-06-12-a
snapshot is working fine. I've also tried to compile the manifest file separately by2020-06-13-a
and2020-06-12-a
versions of the compiler, but using the same version of thelibPackageDescription.dylib
module from either2020-06-13-a
or2020-06-12-a
. Testing these different combinations, I think that the issues is caused bylibPackageDescription.dylib
that became broken in2020-06-13-a
and is still broken in the latest snapshots for bothswiftwasm-release/5.3
andswiftwasm
branches. Looking at file sizes, we can also see that something happened to the library that significantly changed its binary size starting with the2020-06-13-a
snapshot:There don't seem to be any changes between
2020-06-12-a
and2020-06-13-a
in the SwiftPM itself, I think something changed in the compiler that made it miscompile the library.I'm going to research this further, need to investigate what exactly is different between those two compiler versions and how to fix it.
Originally posted by @MaxDesiatov in #1362 (comment)
The text was updated successfully, but these errors were encountered: