<html><body><p>Thanks Pierre.<br><br>We made a little progress on getting tests to compile this afternoon: <a href="https://github.com/dgrove-oss/swift-corelibs-libdispatch/tree/fixtests">https://github.com/dgrove-oss/swift-corelibs-libdispatch/tree/fixtests</a><br><br>Absolutely not ready for a pull request, but mentioning it in case anyone else was starting on the same task and wanted to collaborate. <br><br>--dave<br><br><img width="16" height="16" src="cid:1__=0ABBF58BDFEDB55E8f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Pierre Habouzit ---12/11/2015 12:59:51 PM---> On Dec 11, 2015, at 8:27 AM, David P Grove via swift-co"><font color="#424282">Pierre Habouzit ---12/11/2015 12:59:51 PM---> On Dec 11, 2015, at 8:27 AM, David P Grove via swift-corelibs-dev <swift-corelibs-dev@swift.org> w</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Pierre Habouzit <phabouzit@apple.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">David P Grove/Watson/IBM@IBMUS</font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">Dzianis Fedarenka <f.dz.v.gh@gmail.com>, swift-corelibs-dev@swift.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">12/11/2015 12:59 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [swift-corelibs-dev] libdispatch build issue</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">phabouzit@apple.com</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br>
<ul><ul><font size="4">On Dec 11, 2015, at 8:27 AM, David P Grove via swift-corelibs-dev <</font><a href="mailto:swift-corelibs-dev@swift.org"><u><font size="4" color="#0000FF">swift-corelibs-dev@swift.org</font></u></a><font size="4">> wrote:</font><br>
<p><a href="mailto:swift-corelibs-dev-bounces@swift.org"><tt><u><font size="4" color="#0000FF">swift-corelibs-dev-bounces@swift.org</font></u></tt></a><tt><font size="4"> wrote on 12/11/2015 11:19:15 AM:<br>> <br>> The linux port is in progress, and even if it built, right now, it <br>> wouldn’t be functional.<br>> <br>> -Pierre<br>> <br>> Yes. I completely understand that there linux port is not <br>> functional. So I want to contribute to it. But it's practically <br>> impossible since there is no usable build system :(.</font></tt><font size="4"><br></font><tt><font size="4"><br>It's limping along. We've managed to run a few programs successfully. </font></tt><font size="4"><br></font><tt><font size="4"><br>I think the next step is actually to get the test suite to compile & build so we can see what functionally isn't working yet.</font></tt><font size="4"><br></font><tt><font size="4"><br>Pierre and Daniel, we could use some guidance on how to approach this. The tests have quite a few unguarded includes of mach header files, uses of mach types, and includes of Foundation. How would you like this porting to proceed? Hubertus has already done some initial poking at it, but getting direction on the intended outcome would be very helpful.</font></tt></ul></ul><br><font size="4">We do have an internal test-suite that we can’t share because it rely on internal Apple infrastructure. I haven’t closed the loop with Daniel completely on this but our position I think is that these should be made portable even if that means dropping anything mach related stuff by hiding it behind a #if __APPLE__ or similar.</font><br><br><font size="4">-Pierre</font><br><br><br><BR>
</body></html>