-Pierre > On Dec 14, 2015, at 9:18 AM, Pierre Habouzit via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > Cool, I’ll have a look later this week or when it gets more ready ;) > > btw, we got a pull request that seem good to me > (https://github.com/apple/swift-corelibs-libdispatch/pull/13 > <https://github.com/apple/swift-corelibs-libdispatch/pull/13>) but I don’t > have the linux setup to check it’s good, would you mind review it, I’ve not > seen anything wrong with it from the dispatch or from what I remember from > autotools best practices from my debian developer past.
wow that sentence makes no sense. I meant I see nothing wrong from the dispatch *perspective*. works better with all words ;) > > -Pierre > >> On Dec 11, 2015, at 3:03 PM, David P Grove via swift-corelibs-dev >> <swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org>> wrote: >> >> Thanks Pierre. >> >> We made a little progress on getting tests to compile this afternoon: >> https://github.com/dgrove-oss/swift-corelibs-libdispatch/tree/fixtests >> <https://github.com/dgrove-oss/swift-corelibs-libdispatch/tree/fixtests> >> >> Absolutely not ready for a pull request, but mentioning it in case anyone >> else was starting on the same task and wanted to collaborate. >> >> --dave >> >> <graycol.gif>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 <mailto:swift-corelibs-dev@swift.org>> w >> >> From: Pierre Habouzit <phabou...@apple.com <mailto:phabou...@apple.com>> >> To: David P Grove/Watson/IBM@IBMUS >> Cc: Dzianis Fedarenka <f.dz.v...@gmail.com <mailto:f.dz.v...@gmail.com>>, >> swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> >> Date: 12/11/2015 12:59 PM >> Subject: Re: [swift-corelibs-dev] libdispatch build issue >> Sent by: phabou...@apple.com <mailto:phabou...@apple.com> >> >> >> >> On Dec 11, 2015, at 8:27 AM, David P Grove via swift-corelibs-dev >> <swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org>> wrote: >> swift-corelibs-dev-boun...@swift.org >> <mailto:swift-corelibs-dev-boun...@swift.org> wrote on 12/11/2015 11:19:15 >> AM: >> > >> > The linux port is in progress, and even if it built, right now, it >> > wouldn’t be functional. >> > >> > -Pierre >> > >> > Yes. I completely understand that there linux port is not >> > functional. So I want to contribute to it. But it's practically >> > impossible since there is no usable build system :(. >> >> It's limping along. We've managed to run a few programs successfully. >> >> 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. >> >> 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. >> >> >> 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. >> >> -Pierre >> >> >> >> >> _______________________________________________ >> swift-corelibs-dev mailing list >> swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev > > > _______________________________________________ > swift-corelibs-dev mailing list > swift-corelibs-dev@swift.org > https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
