Open keith opened 1 year ago
might have been fixed by passing -skip-early-swift-driver --skip-early-swiftsyntax
from the docs (must have changed since my last build ~a month ago since I just re-ran my previous command)
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, dispatch/module.modulemap
is no longer placed under source directory of swift-corelibs-libdispatch after https://github.com/apple/swift-corelibs-libdispatch/pull/785, so I just needed to clean the source directory by git clean -f
to repair the build failure.
@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
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