-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Building Swift fails on linux with module redefinition errors #62429
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
Comments
might have been fixed by passing |
I've seen this on Android too, with the prebuilt Swift toolchain package colliding with a trunk toolchain I'm building. The Linux CI doesn't have a prebuilt Swift toolchain, so it doesn't build those early Swift tools, but we'll need to fix this for when building the Swift compiler with a prebuilt Swift compiler becomes mandatory, so keep this open. |
I am just encountering this since the update to swift 5.8. Unfortunately I do require bootstrapping. Any workaround for this? |
This has nothing to do with bootstrapping: it should work if you don't have a prebuilt toolchain in your path, as the linux CI doesn't, or if you pass the two build flags Keith mentioned. |
Just for record, |
@keith, still seeing this or can we close? I haven't seen this in a while, and the linux CI builds with a prebuilt Swift 5.8 toolchain now. |
not sure |
The libdispatch pull Yuta linked should've fixed this, reopen if not. |
When building the Swift compiler on Linux with:
While also having
swiftc
5.7.1 in my$PATH
, I end up getting these build failures:Dispatch
seems to be the first module that fails, but there are many errors with the same issue. Eventually I also see:But I believe the message is correct that the issue is the other duplicate modules.
My impression was that building with an existing Swift compiler installation was expected (or maybe even required), but I am attempting to build without these in my
$PATH
assuming that if it still works that way it won't be able to find these modulemaps, so maybe I'll side step this.Steps to reproduce
Environment
The text was updated successfully, but these errors were encountered: