swift-corelibs-dev-boun...@swift.org wrote on 12/11/2015 03:17:47 AM:
> From: f-dz-f via swift-corelibs-dev
> To: swift-corelibs-dev@swift.org
> Date: 12/11/2015 03:18 AM
> Subject: [swift-corelibs-dev] libdispatch build issue
> Sent by: swift-corelibs-dev-boun...@swift.org
> PS On ubuntu 14.04
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 pr
phaus...@apple.com wrote on 12/11/2015 12:02:30 PM:
> This is only tangentially related: but I was attempting to build
> dispatch as well to start work on CFRunLoop and a few other dispatch
> bound features in Foundation on linux. I was seeing similar failures
> as Dzianis Fedarenka. Is there a bra
:27 AM, David P Grove via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:
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’
swift-corelibs-dev-boun...@swift.org wrote on 03/29/2016 11:58:13 AM:
>
> Hi, everyone
> I follow the command written in INSTALL in
> https://github.com/apple/swift-corelibs-libdispatch/blob/master/INSTALL
>
> sh autogen.sh
>
> ./configure
>
> make
>
> but "make" failed, report is "No rule to ma
I think the intuition about the dispatch overlay being the problem on Linux
is right on. We may have to hack around the problem on the Foundation side
until an improved overlay is available to use.
--dave
From: Philippe Hausler via swift-corelibs-dev
To: Mamatha Busi
Cc:
Hi,
my guess is you missed the git submodule init and update step in
setting up your libdispatch checkout. If the libpwq directory is empty,
this is certainly what happened (and is why it isn't invoking auotconf
recursively on libpwq). Buried at the bottom of the INSTALL file:
Initiali
Hi Joe,
TL;DR: right now the Swift 3.0 overlay for libdispatch is not
available on Linux.
But, a variety of activities are kicking off to get it there. There
should be visible progress (and opportunities to help if you are so
inclined) over the next few weeks.
>
> While working
Joseph Bell wrote on 06/21/2016 09:15:00 AM:
>
> Thanks for the details, I appreciate it. I have seen the term
> "Swift overlay" used, particularly in the context of libdispatch.
> What does that mean exactly in this regard (searching for it returns
> tutorials on overlay UIViews which I doub
Hi,
I've been making some progress on the Swift 3 overlay for dispatch on
a branch [1]. It builds, but doesn't do much more beyond that yet. I
expect to raise a pull request within a week (once basic programs are
working).
--dave
[1]
https://github.com/dgrove-oss/swift-corelibs-libdisp
Hi,
There has been some churn over the last few days, but I am
successfully using util/build-script to build libdispatch with the current
tip of the master branch of libdispatch (and a swift checkout of the master
branch from yesterday morning). Maybe updating the checkout of libdispatch
ok, thanks for the details.
I'll grab the latest myself tomorrow morning and see if I can reproduce.
--dave
From: Jean-Pierre Simard
To: David P Grove/Watson/IBM@IBMUS
Cc: swift-corelibs-dev@swift.org
Date: 07/06/2016 06:21 PM
Subject:Re: Troubleshooting libdispatch build
Tony Parker wrote on 07/28/2016 01:41:55 PM:
>
> 1. Integrate swift-corelibs-dispatch into Foundation.
Hi Tony,
Hopefully this is on the task list already, but if it isn't we should
add it before it gets to be too late to change the compiler...
When compiling a Swift program on
e.
Chris
From: David P Grove via swift-corelibs-dev <
swift-corelibs-dev@swift.org>
To:Swift corelibs dev
Date:28/07/2016 18:50
Subject:Re: [swift-corelibs-dev] Wrapping up Swift 3 for
swift-corelibs
Sent by:
Ryan Lovelett wrote on 08/14/2016 05:10:34 PM:
>
> However, the `dispatch_io` test is still failing. I've added the
> test-suite.log once more.
>
Hi Ryan,
The test that is failing creates a temporary directory, sets it to be
read-only, and then attempts to write into the directory. I
I've never seen this test fail before. We haven't changed the kqueue git
submodule version since July 20. It looks like the next 20 runs of this CI
build didn't hit this test failure either.
I took a quick scan of the kqueue tests and like some of the other
libdispatch test cases, the kqueue t
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.
--dave
From: Jordan Rose
To: David P Grove/Watson/IBM@IBMUS
Cc: "Daniel
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'
I think the root problem is that some of the dispatch tests, including this
one, are trying to test that timers/events happen within a "reasonable"
interval of time from when they are supposed to. If deadlines are missed
too badly, then the test is marked as failing.
If we completely disabled al
swift-dev-boun...@swift.org wrote on 05/17/2017 02:04:23 PM:
>
> Failure in dispatch-starfish. This test looks timing-sensitive.
> Boris, is this unlikely to be related to your changes? Does anyone
> familiar with dispatch have suggestions, such as increasing the
> latency threshold?
>
> [BEGIN]
20 matches
Mail list logo
