Hi Atul, The master branch is tested in CI, so any build failures are likely due to configuration problems on your end. While testing the swift-4.0-branch would provide an interesting data point, I would not expect it to work if building master fails.
Slava > On Oct 8, 2017, at 10:35 PM, Atul Sowani via swift-dev <swift-dev@swift.org> > wrote: > > I still have no luck building swift on x86 using the master branch. Is it > recommended to use the master branch at all (considering a lot of fixes would > be coming in) or is it desirable to use 4.0 branch instead as a general rule? > > Thanks, > Atul. > > On Fri, Oct 6, 2017 at 7:03 PM, Atul Sowani via swift-dev > <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote: > Thanks Alex! I used the clean/reset command and then tried rebuilding it, but > got the very same error. I am using master branch, latest (top-of-the-tree) > version: > > git clone https://github.com/apple/swift.git > <https://github.com/apple/swift.git> > ./swift/utils/update-checkout --clone > cd swift > utils/build-script -c -m -R --verbose-build > > Hope this is correct. > > Thanks, > Atul. > > On Fri, Oct 6, 2017 at 5:51 PM, Alex Blewitt <alb...@apple.com > <mailto:alb...@apple.com>> wrote: > > > > On 6 Oct 2017, at 12:42, Atul Sowani via swift-dev <swift-dev@swift.org > > <mailto:swift-dev@swift.org>> wrote: > > > > Hi, > > > > Swift "master" branch is failing to build on x86 running Ubuntu 16,04 with > > following error. > > Most of the recent builds appear to be working: > > https://ci.swift.org/view/swift-master-next/job/oss-swift-incremental-RA-linux-ubuntu-16_04-master-next/ > > <https://ci.swift.org/view/swift-master-next/job/oss-swift-incremental-RA-linux-ubuntu-16_04-master-next/> > > > I am using following build command from inside swift-source/swift directory: > > utils/build-script -c -m -R --verbose-build > > What version of the 'swift' project do you have checked out? Have you done a > clean/reset to make sure those aren't issues at the moment? > > You can run swift/utils/update-checkout --clean --reset-to-remote --scheme > master (which will get rid of any cruft if you haven't got anything you need > to keep) and then re-run the build to see if that resolves the errors. > > Alex > > > _______________________________________________ > swift-dev mailing list > swift-dev@swift.org <mailto:swift-dev@swift.org> > https://lists.swift.org/mailman/listinfo/swift-dev > <https://lists.swift.org/mailman/listinfo/swift-dev> > > > _______________________________________________ > 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
