Re: [swift-dev] Building a swift release

2017-11-16 Thread Timothy Wood via swift-dev
I had to go spelunking in the build scripts to find this, so no idea if it is the proper way, but it seems to work. In a fresh checkout of the swift repo: ./utils/update-checkout --clone --scheme swift-4.0-branch This will clone all the needed repos and then check out the right branch.

[swift-dev] SR-1406: Xcode crashing while indexing

2016-05-13 Thread Timothy Wood via swift-dev
I’m still hitting https://bugs.swift.org/browse/SR-1406 with the latest Swift 3 snapshot. To try to help track this down, I’ve build a local snapshot with a trimmed down version of `./utils/build-toolchain local.swift` (just removing the stuff that looked test related): % ./utils/build-script

Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on Pi from source

2016-04-19 Thread Timothy Wood via swift-dev
> On Apr 17, 2016, at 11:33 PM, Timothy Wood via swift-dev > wrote: > > I might try again tomorrow updating to a newer clang build, or maybe I should > just wave the white flag and rewrite my tiny codebase in C++ instead of > trying to use Swift here, and wait for it to be

Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on Pi from source

2016-04-17 Thread Timothy Wood via swift-dev
> On Apr 17, 2016, at 1:46 PM, Timothy Wood via swift-dev > wrote: > > >> On Apr 16, 2016, at 2:23 PM, William Dillon > <mailto:will...@housedillon.com>> wrote: >> >> What LLVM are you using? >> >> You have to use the one from my gith

Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on Pi from source

2016-04-17 Thread Timothy Wood via swift-dev
> On Apr 15, 2016, at 6:45 PM, Joe Groff wrote: > What linker are you using? GNU ld 2.26 in particular changed the behavior of > protected visibility in a way that's incompatible with our usage, and we > haven't fully implemented a workaround. You might try using gold or an older > binutils, i

[swift-dev] Random failure when building Swift on Pi

2016-04-17 Thread Timothy Wood via swift-dev
I’m encountering random build compile failures when building on Pi, using clang-3.6 (as suggested in the various instructions to do so), and when using One example looks like: FAILED: /usr/bin/clang++ -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE

Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on Pi from source

2016-04-17 Thread Timothy Wood via swift-dev
> On Apr 16, 2016, at 2:23 PM, William Dillon wrote: > > What LLVM are you using? > > You have to use the one from my github (and the arm branch) or it won't work: > > https://github.com/hpux735/swift-llvm/tree/arm > > > I haven't had time to

[swift-dev] R_ARM_GOT_PREL error when building Swift on Pi from source

2016-04-15 Thread Timothy Wood via swift-dev
I was able to get Swift running on my Raspberry Pi using a variant of the instructions at but sadly the packages I’ve found haven’t been updated for Swift 2.2 (so things like `associatedtype` don’t work nicely between M

[swift-dev] Advice on SR-580?

2016-03-19 Thread Timothy Wood via swift-dev
Looking through the ‘StarterBug’ tag, I started looking into >, in which: func foo(x: Int) -> Int { var result = x + 1 #if NOT_ENABLED _ = result #endif return result } does not warn that “result" was never written t