You can use ./swift/utils/update-checkout --scheme swift-3.1-branch which will switch the branches to the right place for you. Some of the git repositories aren't necessarily the same; using the update-checkout script to select the right ones will be more successful. You can also use --reset-to-remote if you've made local changes that you want to throw away or want to ensure that it does the right thing from a clean update.
Alex > On 25 Apr 2017, at 13:26, Ian Partridge via swift-dev <swift-dev@swift.org> > wrote: > > Hi, I'm trying to build a toolchain from swift-3.1-branch on Linux. > > I cloned https://github.com/apple/swift and ran > "./swift/utils/update-checkout --clone" successfully. > > Then, for each subdirectory (swift, swift-corelibs-foundation, lldb, > llvm etc.) I switched to swift-3.1-branch via "git checkout > swift-3.1-branch". > > Then I ran: > > ./swift/utils/build-script --preset=buildbot_linux > install_destdir=/home/ipartrid/swift-3.1 > installable_package=/home/ipartrid/swift-3.1.tar.gz > > But this fails with: > > Traceback (most recent call last): > File "./swift/utils/build-script", line 27, in <module> > from SwiftBuildSupport import ( > File "/home/ipartrid/swift-source/swift/utils/SwiftBuildSupport.py", > line 26, in <module> > from swift_build_support import diagnostics # noqa (E402) > ImportError: cannot import name diagnostics > > Can anyone advise on how to build swift-3.1-branch? I'm pretty sure > my procedure above used to work, until recently. > > Many thanks, > > -- > Ian Partridge > _______________________________________________ > swift-dev mailing list > swift-dev@swift.org > https://lists.swift.org/mailman/listinfo/swift-dev _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
