<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">The problem with moving the Darwin Dispatch overlay there is that other overlays depend on Dispatch, and we’re not ready to move those out somewhere else. That would compound this cross-repo dependency problem.</div><div class=""><br class=""></div><div class="">Jordan</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 26, 2016, at 12:32, Daniel A. Steffen <<a href="mailto:dsteffen@apple.com" class="">dsteffen@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">this may be an unintended consequence of us putting the Linux overlay into the library repo (as opposed to the compiler repo).</div><div class=""><br class=""></div><div class="">I still think that is the right place for the overlay to live though, and that we should move the Darwin overlay there as well medium term (and work out any resulting build issues).</div><div class=""><br class=""></div><div class="">On both platforms we want to move towards a more integrated support for the Swift 3 interfaces directly from the library instead of the large overlay we have now.</div><div class=""><br class=""></div><div class="">Daniel</div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Sep 26, 2016, at 10:19, David P Grove via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><p class="">We think that the libdispatch incremental rebuilds didn't know that if swiftc changed it needed to invalidate the compilation of the swift dispatch overlay files (missing dependency in the make rule). A localized change that could be enough to fix the problem is libdispatch PR #178. If that isn't enough, we might have to do a more ambitious restructuring of the libdispatch build.<br class=""><br class="">--dave<br class=""><br class=""><span id="cid:1__=0ABB0AA9DFCDBA5D8f9e8a93df938690918c0AB@" class=""><graycol.gif></span><font color="#424282" class="">Jordan Rose ---09/26/2016 01:07:24 PM---Oh, I didn’t realize we had a separate copy of the overlay code (almost certainly the right thing to</font><br class=""><br class=""><font size="2" color="#5F5F5F" class="">From: </font><font size="2" class="">Jordan Rose <<a href="mailto:jordan_rose@apple.com" class="">jordan_rose@apple.com</a>></font><br class=""><font size="2" color="#5F5F5F" class="">To: </font><font size="2" class="">David P Grove/Watson/IBM@IBMUS</font><br class=""><font size="2" color="#5F5F5F" class="">Cc: </font><font size="2" class="">"Daniel A. Steffen" <<a href="mailto:dsteffen@apple.com" class="">dsteffen@apple.com</a>>, swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>>, swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>></font><br class=""><font size="2" color="#5F5F5F" class="">Date: </font><font size="2" class="">09/26/2016 01:07 PM</font><br class=""><font size="2" color="#5F5F5F" class="">Subject: </font><font size="2" class="">Re: [swift-dev] Swift CI PR builder dispatch linux failure</font><br class=""><font size="2" color="#5F5F5F" class="">Sent by: </font><font size="2" class=""><a href="mailto:jordan_rose@apple.com" class="">jordan_rose@apple.com</a></font><br class=""></p><hr width="100%" size="2" align="left" noshade="" style="color:#8091A5; " class=""><br class=""><br class=""><br class=""><font size="4" class="">Oh, I didn’t realize we had a separate copy of the overlay code (almost certainly the right thing to do at this point). But in that case, why are we seeing any of these errors?</font><br class=""><br class=""><font size="4" class="">Jordan</font><br class="">
<ul class=""><ul class=""><font size="4" class="">On Sep 25, 2016, at 11:38, David P Grove <</font><a href="mailto:groved@us.ibm.com" class=""><u class=""><font size="4" color="#0000FF" class="">groved@us.ibm.com</font></u></a><font size="4" class="">> wrote:</font><br class=""><p class=""><font size="4" class="">The order may need to vary by platform. On Linux, the DIspatch Swift overlay code lives in swift-corelibs-libdispatch/src/swift. So it works to build (1) Swift (2) libdispatch (both C and Swift) (3) Foundation. <br class=""><br class="">--dave<br class=""><br class=""><graycol.gif></font><font size="4" color="#424282" class="">Jordan Rose ---09/23/2016 06:34:46 PM---I think the right order to build things is: 1. libdispatch (C)</font><font size="4" class=""><br class=""></font><font color="#5F5F5F" class=""><br class="">From: </font>Jordan Rose <<a href="mailto:jordan_rose@apple.com" class=""><u class=""><font color="#0000FF" class="">jordan_rose@apple.com</font></u></a>><font color="#5F5F5F" class=""><br class="">To: </font>David P Grove/Watson/IBM@IBMUS<font color="#5F5F5F" class=""><br class="">Cc: </font>"Daniel A. Steffen" <<a href="mailto:dsteffen@apple.com" class=""><u class=""><font color="#0000FF" class="">dsteffen@apple.com</font></u></a>>, swift-dev <<a href="mailto:swift-dev@swift.org" class=""><u class=""><font color="#0000FF" class="">swift-dev@swift.org</font></u></a>>, swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class=""><u class=""><font color="#0000FF" class="">swift-corelibs-dev@swift.org</font></u></a>><font color="#5F5F5F" class=""><br class="">Date: </font>09/23/2016 06:34 PM<font color="#5F5F5F" class=""><br class="">Subject: </font>Re: [swift-dev] Swift CI PR builder dispatch linux failure<font color="#5F5F5F" class=""><br class="">Sent by: </font><a href="mailto:jordan_rose@apple.com" class=""><u class=""><font color="#0000FF" class="">jordan_rose@apple.com</font></u></a></p><div class=""><br class="webkit-block-placeholder"></div><hr width="100%" size="2" align="left" noshade="" class=""><font size="4" class=""><br class=""><br class=""></font><font size="5" class=""><br class="">I think the right order to build things is:</font><font size="4" class=""><br class=""></font><font size="5" class=""><br class="">1. libdispatch (C)<br class="">2. Swift (compiler + stdlib + Dispatch overlay)<br class="">3. Foundation</font><font size="4" class=""><br class=""></font><font size="5" class=""><br class="">Otherwise we need to build Swift, then build libdispatch, then go back to "Swift" to build the overlay, and only finally get to Foundation.</font><font size="4" class=""><br class=""></font><font size="5" class=""><br class="">Jordan</font><font size="4" class=""><br class=""></font><ul class=""><ul class=""><ul class=""><ul class=""><font size="5" class="">On Sep 23, 2016, at 14:32, David P Grove via swift-dev <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="5" color="#0000FF" class="">swift-dev@swift.org</font></u></a><font size="5" class="">> wrote:</font><p class=""><font size="5" class="">I'm playing with something. Should have a PR ready shortly.<br class=""><br class="">--dave<br class=""><br class=""><br class=""><graycol.gif></font><font size="5" color="#424282" class="">"Daniel A. Steffen via swift-dev" ---09/23/2016 04:45:06 PM---I don’t know how these dependencies are expressed in CMake but it doesn’t seem very difficult to do</font><font size="4" color="#5F5F5F" class=""><br class=""><br class="">From: </font><font size="4" class="">"Daniel A. Steffen via swift-dev" <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="4" color="#0000FF" class="">swift-dev@swift.org</font></u></a><font size="4" class="">></font><font size="4" color="#5F5F5F" class=""><br class="">To: </font><font size="4" class="">Ted Kremenek <</font><a href="mailto:kremenek@apple.com" class=""><u class=""><font size="4" color="#0000FF" class="">kremenek@apple.com</font></u></a><font size="4" class="">></font><font size="4" color="#5F5F5F" class=""><br class="">Cc: </font><font size="4" class="">swift-dev <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="4" color="#0000FF" class="">swift-dev@swift.org</font></u></a><font size="4" class="">></font><font size="4" color="#5F5F5F" class=""><br class="">Date: </font><font size="4" class="">09/23/2016 04:45 PM</font><font size="4" color="#5F5F5F" class=""><br class="">Subject: </font><font size="4" class="">Re: [swift-dev] Swift CI PR builder dispatch linux failure</font><font size="4" color="#5F5F5F" class=""><br class="">Sent by: </font><a href="mailto:swift-dev-bounces@swift.org" class=""><u class=""><font size="4" color="#0000FF" class="">swift-dev-bounces@swift.org</font></u></a></p><p class=""><br class=""></p><hr width="100%" size="2" align="left" noshade="" class=""><font size="5" class=""><br class=""></font><font size="6" class=""><br class=""><br class="">I don’t know how these dependencies are expressed in CMake but it doesn’t seem very difficult to do so in the autotools buildsystem, we have<br class=""><br class="">AC_ARG_WITH([swift-toolchain],<br class="">[AS_HELP_STRING([--with-swift-toolchain], [Specify path to Swift toolchain])],<br class="">[swift_toolchain_path=${withval}<br class="">AC_DEFINE(HAVE_SWIFT, 1, [Define if building for Swift])<br class="">SWIFTC="$swift_toolchain_path/bin/swiftc”<br class=""><br class="">in configure.ac which ends up as a SWIFTC makefile variable, so as long as that argument is passed as an absolute path, it should work as a dependency in the build rules<br class=""><br class="">$(abs_builddir)/swift/%.o: $(abs_srcdir)/swift/%.swift<br class="">$(SWIFTC) -frontend -c $(SWIFT_ABS_SRC_FILES) -primary-file $< \<br class=""><br class="">Is there a JIRA ticket for this ? the IBM folks should probably be the ones making these changes since we still don’t have the whitelist in place for Apple contributors to do so…<br class=""><br class="">Daniel</font><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><font size="6" class="">On Sep 23, 2016, at 13:00, Ted Kremenek <</font><a href="mailto:kremenek@apple.com" class=""><u class=""><font size="6" color="#0000FF" class="">kremenek@apple.com</font></u></a><font size="6" class="">> wrote:<br class=""><br class="">+ Daniel</font><b class=""><font size="6" class=""><br class=""><br class="">Daniel</font></b><font size="6" class="">: how hard would it be for the Dispatch project to be modified to add the swiftc binary used to build the project as a dependency?</font><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><font size="6" class="">On Sep 23, 2016, at 12:55 PM, Ted Kremenek via swift-dev <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="6" color="#0000FF" class="">swift-dev@swift.org</font></u></a><font size="6" class="">> wrote:<br class=""><br class="">Dispatch is a separate project. There isn’t a dependency in the Dispatch project to tell it is building with a new compiler. The project would need to be modified to add a dependency on the swiftc binary being used to compile this project.</font><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><font size="6" class="">On Sep 21, 2016, at 9:39 AM, Mishal Shah via swift-dev <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="6" color="#0000FF" class="">swift-dev@swift.org</font></u></a><font size="6" class="">> wrote:<br class=""><br class="">We should look into why it's not rebuilding dependencies. Do we need to fix CMake logic? Can you please file a bug?</font><font size="5" class=""><br class=""></font><font size="6" class=""><br class=""><br class="">Thanks,<br class="">Mishal Shah<br class=""><br class="">On Sep 21, 2016, at 9:28 AM, Michael Gottesman <</font><a href="mailto:mgottesman@apple.com" class=""><u class=""><font size="6" color="#0000FF" class="">mgottesman@apple.com</font></u></a><font size="6" class="">> wrote:</font><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><font size="6" class="">+CC Mishal</font><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><ul class=""><font size="6" class="">On Sep 21, 2016, at 6:59 AM, David P Grove via swift-dev <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="6" color="#0000FF" class="">swift-dev@swift.org</font></u></a><font size="6" class="">> wrote:</font><p class=""><font size="4" face="Helvetica" class="">I don't know how the PR jobs are setup, but the error suggests that they are trying to reuse too much of the workspace of previous runs.</font><font size="7" color="#FFFFFF" face="Helvetica" class=""><br class=""><br class=""><</font><font size="7" face="Helvetica" class="">unknown>:0: error: module file was created by an older version of the compiler; rebuild 'Dispatch' and try again: /home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src/swift/Dispatch.o.~partial.swiftmodule<br class=""><br class="">--dave</font><font size="4" face="Helvetica" class=""><br class=""><br class=""><br class=""><graycol.gif></font><font size="4" color="#424282" face="Helvetica" class="">Ankit Aggarwal via swift-dev ---09/21/2016 03:08:58 AM---This has been consistently failing on PRs, can someone look into this: <unknown>:0: error: module fi</font><font size="5" color="#5F5F5F" face="Helvetica" class=""><br class=""><br class="">From: </font><font size="5" face="Helvetica" class="">Ankit Aggarwal via swift-dev <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="5" color="#0000FF" face="Helvetica" class="">swift-dev@swift.org</font></u></a><font size="5" face="Helvetica" class="">></font><font size="5" color="#5F5F5F" face="Helvetica" class=""><br class="">To: </font><font size="5" face="Helvetica" class="">swift-dev <</font><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="5" color="#0000FF" face="Helvetica" class="">swift-dev@swift.org</font></u></a><font size="5" face="Helvetica" class="">></font><font size="5" color="#5F5F5F" face="Helvetica" class=""><br class="">Date: </font><font size="5" face="Helvetica" class="">09/21/2016 03:08 AM</font><font size="5" color="#5F5F5F" face="Helvetica" class=""><br class="">Subject: </font><font size="5" face="Helvetica" class="">[swift-dev] Swift CI PR builder dispatch linux failure</font><font size="5" color="#5F5F5F" face="Helvetica" class=""><br class="">Sent by: </font><a href="mailto:swift-dev-bounces@swift.org" class=""><u class=""><font size="5" color="#0000FF" face="Helvetica" class="">swift-dev-bounces@swift.org</font></u></a></p><div class=""><br class="webkit-block-placeholder"></div><div class=""><br class="webkit-block-placeholder"></div><hr width="100%" size="2" align="left" noshade="" class=""><font size="7" face="Helvetica" class=""><br class=""><br class=""><br class="">This has been consistently failing on PRs, can someone look into this:</font><tt class=""><font size="4" color="#FFFFFF" class=""><br class=""><br class=""><unknown>:0: error: module file was created by an older version of the compiler; rebuild 'Dispatch' and try again: /home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src/swift/Dispatch.o.~partial.swiftmodule</font></tt><tt class=""><font size="4" color="#C0C5CE" class=""><br class="">make[2]: *** [/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src/swift/Dispatch.swiftmodule] Error 1<br class="">make[2]: Leaving directory `/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src'<br class="">make[1]: *** [all] Error 2<br class="">make[1]: Leaving directory `/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src'<br class="">make: *** [all-recursive] Error 1<br class="">/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/swift/utils/build-script: fatal error: command terminated with a non-zero exit status 2, aborting<br class="">/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting</font></tt><u class=""><font size="4" color="#0000FF" face="Helvetica" class=""><br class=""></font></u><u class=""><font size="5" color="#0000FF" class=""><br class=""></font></u><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="https://ci.swift.org/job/swift-package-manager-PR-Linux/497/console" class=""><u class=""><font size="7" color="#0000FF" face="Helvetica" class="">https://ci.swift.org/job/swift-package-manager-PR-Linux/497/console</font></u></a><font size="5" face="Helvetica" class=""><br class=""><br class="">- Ankit</font><font size="7" face="Helvetica" class=""> </font><font size="4" face="Helvetica" class=""><br class="">[attachment "signature.asc" deleted by David P Grove/Watson/IBM] </font><tt class=""><font size="4" class="">_______________________________________________<br class="">swift-dev mailing list</font></tt><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="mailto:swift-dev@swift.org" class=""><tt class=""><u class=""><font size="4" color="#0000FF" class="">swift-dev@swift.org</font></u></tt></a><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class=""><tt class=""><u class=""><font size="4" color="#0000FF" class="">https://lists.swift.org/mailman/listinfo/swift-dev</font></u></tt></a><font size="6" class=""><br class=""></font><font size="4" face="Helvetica" class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">swift-dev mailing list</font><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="4" color="#0000FF" face="Helvetica" class="">swift-dev@swift.org</font></u></a><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class=""><u class=""><font size="4" color="#0000FF" face="Helvetica" class="">https://lists.swift.org/mailman/listinfo/swift-dev</font></u></a></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul><font size="6" class="">_______________________________________________<br class="">swift-dev mailing list</font><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="6" color="#0000FF" class="">swift-dev@swift.org</font></u></a><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class=""><u class=""><font size="6" color="#0000FF" class="">https://lists.swift.org/mailman/listinfo/swift-dev</font></u></a></ul></ul></ul></ul></ul></ul></ul></ul><font size="6" class=""><br class="">_______________________________________________<br class="">swift-dev mailing list</font><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="6" color="#0000FF" class="">swift-dev@swift.org</font></u></a><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class=""><u class=""><font size="6" color="#0000FF" class="">https://lists.swift.org/mailman/listinfo/swift-dev</font></u></a></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul></ul><tt class=""><font size="5" class="">_______________________________________________<br class="">swift-dev mailing list</font></tt><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="mailto:swift-dev@swift.org" class=""><tt class=""><u class=""><font size="5" color="#0000FF" class="">swift-dev@swift.org</font></u></tt></a><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class=""><tt class=""><u class=""><font size="5" color="#0000FF" class="">https://lists.swift.org/mailman/listinfo/swift-dev</font></u></tt></a><font size="5" class=""><br class=""><br class=""></font><font size="4" class=""><br class=""></font><font size="5" class=""><br class="">_______________________________________________<br class="">swift-dev mailing list</font><u class=""><font size="4" color="#0000FF" class=""><br class=""></font></u><a href="mailto:swift-dev@swift.org" class=""><u class=""><font size="5" color="#0000FF" class="">swift-dev@swift.org</font></u></a><u class=""><font size="5" color="#0000FF" class=""><br class=""></font></u><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class=""><u class=""><font size="5" color="#0000FF" class="">https://lists.swift.org/mailman/listinfo/swift-dev</font></u></a></ul></ul></ul></ul><font size="4" class=""><br class=""><br class=""></font></ul></ul><br class=""><br class=""><br class="">
</div>
_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-dev" class="">https://lists.swift.org/mailman/listinfo/swift-dev</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></body></html>