[swift-dev] Standard Library not built in release mode with -R in build script

Standard library is not built in release mode by default with -R flag in build script. Is that intended behaviour? Passing `--no-swift-stdlib-assertions --build-swift-static-stdlib --swift-enable-ast-verifier=0` to build script created the build in folder `Ninja-ReleaseAssert+stdlib-Release` --

Re: [swift-dev] Could not find a package configuration file provided by "Clang"

Somewhat wild guess. What is the version of your cmake install? I think we started requiring some 3ish version recently. Maybe you need a newer version … > On Jul 20, 2016, at 2:07 PM, Erica Sadun via swift-dev > wrote: > > I started with an absolutely clean re-clone, used bash (normally I us

Re: [swift-dev] Standard Library not built in release mode with -R in build script

On Thu, Jul 21, 2016 at 8:35 AM, Ankit Agarwal via swift-dev wrote: > Standard library is not built in release mode by default with -R flag in > build script. Is that intended behaviour? > > Passing `--no-swift-stdlib-assertions --build-swift-static-stdlib > --swift-enable-ast-verifier=0` to build

Re: [swift-dev] Standard Library not built in release mode with -R in build script

Got it, thanks! On Thu, Jul 21, 2016 at 9:08 PM, Dmitri Gribenko wrote: > On Thu, Jul 21, 2016 at 8:35 AM, Ankit Agarwal via swift-dev > wrote: > > Standard library is not built in release mode by default with -R flag in > > build script. Is that intended behaviour? > > > > Passing `--no-swift-

Re: [swift-dev] [swift-evolution] Endgame for Swift 3

Is there any way to tell which of the changes in the gist have had proposals associated with them? -- Will On Fri, Jul 15, 2016 at 1:46 PM Ted Kremenek via swift-evolution < swift-evolut...@swift.org> wrote: > Hi everyone, > > Swift 3 has shaped up to be a remarkable release — a product of the >

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 - Long Test (master) #535

Looks like a missing #include . - Doug > On Jul 15, 2016, at 4:41 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10-long-test [#535] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10-long-test/535/ > >

Re: [swift-dev] Could not find a package configuration file provided by "Clang"

Yes. 3.4.3. Michael > On Jul 21, 2016, at 8:37 AM, Arnold Schwaighofer via swift-dev > wrote: > > Somewhat wild guess. What is the version of your cmake install? > > I think we started requiring some 3ish version recently. > > Maybe you need a newer version … > >> On Jul 20, 2016, at 2:07 P

[swift-dev] CI trigger request

Could someone kindly trigger CI again for me? https://github.com/apple/swift/pull/3637 Jacob ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] CI trigger request

I kicked it off. - Tony > On Jul 21, 2016, at 1:08 PM, Jacob Bandes-Storch via swift-dev > wrote: > > Could someone kindly trigger CI again for me? > https://github.com/apple/swift/pull/3637 > > > Jacob > ___

Re: [swift-dev] CI trigger request

Is there something special I need to do to make CI automatically use the latest commits from swift-package-manager and swift-corelibs-foundation? The SwiftPM build seemed to fail again with the same error it had the first time: https://ci.swift.org/job/swift-PR-osx/2642/console But I already fixe

Re: [swift-dev] CI trigger request

Just kidding, this is another instance of the same error. Will require a separate fix. On Thu, Jul 21, 2016 at 2:45 PM, Jacob Bandes-Storch wrote: > Is there something special I need to do to make CI automatically use the > latest commits from swift-package-manager and swift-corelibs-foundation?

Re: [swift-dev] Turns out Incremental builds were not actually incremental

IIRC this was deliberate because of some past issues with things not getting rebuilt. In particular, even an incremental build should trash the module cache folder every build, and I don’t think we do this. Nicole, do you remember specifically why this was changed? (Or Mishal, when back from vac

Re: [swift-dev] Turns out Incremental builds were not actually incremental

> On Jul 21, 2016, at 2:54 PM, Jordan Rose wrote: > > IIRC this was deliberate because of some past issues with things not getting > rebuilt. In particular, even an incremental build should trash the module > cache folder every build, and I don’t think we do this. Nicole, do you > remember sp

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (master) #6389

Something is fishy here… looks like Foundation is getting a stale standard library somehow. I’ve cleared the workspace. - Doug > On Jul 21, 2016, at 3:32 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#6389] > > Build URL: > https://ci.swif

Re: [swift-dev] Turns out Incremental builds were not actually incremental

> On Jul 21, 2016, at 15:06, Michael Gottesman wrote: > > >> On Jul 21, 2016, at 2:54 PM, Jordan Rose wrote: >> >> IIRC this was deliberate because of some past issues with things not getting >> rebuilt. In particular, even an incremental build should trash the module >> cache folder every

Re: [swift-dev] CI trigger request

Next, could someone take care of https://github.com/apple/swift-package-manager/pull/519 ? Thanks in advance, Jacob On Thu, Jul 21, 2016 at 2:47 PM, Jacob Bandes-Storch wrote: > Just kidding, this is another instance of the same error. Will require a > separate fix. > > On Thu, Jul 21, 2016 at

[swift-dev] Reflection/typeref_lowering.swift' FAILED (but not on Swift CI)

Has anyone else seen this failure on darwin building the latest github/master? commit d78012b03feaa5c946fd7d5254ff9492457f1874 (HEAD -> master, public/master) TEST 'Swift :: Reflection/typeref_lowering.swift' FAILED /s/sptr/swift/test/Reflection/typeref_l

Re: [swift-dev] Could not find a package configuration file provided by "Clang"

3.6.0 -- E > On Jul 21, 2016, at 9:37 AM, Arnold Schwaighofer > wrote: > > Somewhat wild guess. What is the version of your cmake install? > > I think we started requiring some 3ish version recently. > > Maybe you need a newer version … > >> On Jul 20, 2016, at 2:07 PM, Erica Sadun via swif