Open swift-ci opened 8 years ago
@gribozavr, @shahmishal, any ideas?
I don't think we have any Makefile buildbots. So it is not a surprise for me that this configuration is broken.
srcshelton (JIRA User), is there a reason why you can't use ninja?
Comment by Stuart Shelton (JIRA)
Building with Ninja failed during compilation, whereas with '-m' compilation succeeded, but installation failed... I guessed that this would be the easier problem to address 😉
If the way I'm invoking the build-script looks reasonable, though, I can file a bug for the issue with ninja - I'll just have to rebuild in order to capture the failure.
Is the '-m' option something that is intended to be supported, or is it going away?
Comment by Stuart Shelton (JIRA)
SR-1259 for error building with Ninja.
Environment
Linux x86_64Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | | |Labels | Bug, Linux | |Assignee | None | |Priority | Medium | md5: 848c1809d27c209d605b434404086e65Issue Description:
When not using ninja, swift-2.2-RELEASE appears to successfully compile before producing the output:
... having been invoked as:
... and indeed, /var/tmp/swift-2.2/work/build/Unix_Makefiles-Release/swift-linux-x86_64/Makefile contains 'preinstall' rules, but makes no mention of 'install'.
I've tried to derive the build process from the available documentation and the scripts in the utils directory, but there seems to be very little information around concerning building the release version of swift from source. If the above is intended operation, could someone suggest how to install swift after compilation has apparently succeeded?