-
Notifications
You must be signed in to change notification settings - Fork 10.5k
module reserialization does not load VFS mappings #79839
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Android
Platform: Android
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
module maps
serialization
Area → compiler: Serialization & deserialization
Windows
Platform: Windows
Comments
CC: @xymus |
compnerd
added a commit
to compnerd/apple-swift
that referenced
this issue
Mar 7, 2025
These cannot be reserialized due to a bug in the serialization logic where we do not inject the VFS Ovelay for the system modules. Bug: swiftlang#79839
compnerd
added a commit
to compnerd/swift-installer-scripts
that referenced
this issue
Mar 7, 2025
Remove the distribution of the resilient swift module interface due to a bug in the reserialization process. Bug: swiftlang/swift#79839
I do not see this error on my Android CI, which runs on linux. Could this be related to the Swift compiler running on Windows, or the unique SDK layout you are using for Android there instead? Btw, I never heard back from you if the final version of #74814 is working for your TBC builds now, would be good to sew that up. |
compnerd
added a commit
to compnerd/apple-swift
that referenced
this issue
Mar 10, 2025
These cannot be re-serialized due to a bug in the serialization logic where we do not inject the VFS overlay for the system modules. Bug: swiftlang#79839
weliveindetail
pushed a commit
to weliveindetail/swift
that referenced
this issue
Mar 11, 2025
These cannot be re-serialized due to a bug in the serialization logic where we do not inject the VFS overlay for the system modules. Bug: swiftlang#79839
weliveindetail
pushed a commit
to weliveindetail/swift
that referenced
this issue
Mar 13, 2025
These cannot be re-serialized due to a bug in the serialization logic where we do not inject the VFS overlay for the system modules. Bug: swiftlang#79839
hjyamauchi
added a commit
to hjyamauchi/swift
that referenced
this issue
Mar 14, 2025
To fix the Android build issue swiftlang#79839
hjyamauchi
added a commit
to hjyamauchi/swift
that referenced
this issue
Mar 14, 2025
To fix the Android build issue swiftlang#79839
weliveindetail
pushed a commit
to weliveindetail/swift
that referenced
this issue
Mar 15, 2025
These cannot be re-serialized due to a bug in the serialization logic where we do not inject the VFS overlay for the system modules. Bug: swiftlang#79839
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Android
Platform: Android
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
module maps
serialization
Area → compiler: Serialization & deserialization
Windows
Platform: Windows
Description
When re-serializing a swiftinterface to a swiftmodule, we do not inject the VFS overlay mappings for custom overlays (i.e. android.modulemap, ucrt.modulemap, winsdk.modulemap, visualc.modulemap). This results in the failure to "find" modules that are required.
Reproduction
Checkout cc145482 and matching version from interface-bug-checkouts.log
From your source root, start the build:
Explanation:
usr\lib\swift\android\_math.swiftmodule
lacks the "underlying Objective-C module '_math'"usr\lib\swift\android\Android.swiftmodule
lacks the "SwiftAndroid" module, which is a Clang ModuleThese dependencies are defined in the android.modulemap, which can be found in subfolder
usr/lib/swift/android/x86_64
of the just-built SDK.Expected behavior
Environment
Additional information
Workaround is to remove all
*.swiftinterface
files from the Android SDK folder. This will force the compiler to use the binary swift modules, which should work.The text was updated successfully, but these errors were encountered: