Re: [swift-dev] Why are we re-linking?

Sorry, accidentally clicked send button.. I've wrote PoC code here: https://github.com/rintaro/swift/commit/9bf18d46f4933ace03948417087bade084104edb Of course, this changes the semantics of `--version` output. So I'm not sure we can accept this or not. Any thought? Rintaro 2016-05-06 13:08 GMT+

Re: [swift-dev] Why are we re-linking?

Hi all, getSwiftFullVersion output must take account stdlib revsion? How about get the revision hash from the Swift repository *excluding* stdlib/, test/ and validation-test/ directories. git log -1 --pretty=format:%H -- \ . \ :(exclude)stdlib \ :(exclude)test \ :(exclude)validat

Re: [swift-dev] swift (ABI) and Windows

> On May 5, 2016, at 4:18 PM, Sangjin Han via swift-dev > wrote: > > Hi, > > I made an experimental MSVC port. Of cause, dllimport/dllexport and the > driver for linking and many other part is not implemented. But dynamic > linking was possible with some trick. > > I think it is useful for

Re: [swift-dev] Linux test failure

Awesome, thanks! - Daniel > On May 5, 2016, at 4:17 PM, Mark Lacey wrote: > > >> On May 5, 2016, at 12:36 PM, Daniel Dunbar via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Anyone know what is up with this Linux test failure? We keep seeing it block >> @swift-ci merges: >> Failin

Re: [swift-dev] swift (ABI) and Windows

Hi, I made an experimental MSVC port. Of cause, dllimport/dllexport and the driver for linking and many other part is not implemented. But dynamic linking was possible with some trick. I think it is useful for designing, my observation about the experimental building of libswiftCore.dll, libswift

Re: [swift-dev] Linux test failure

> On May 5, 2016, at 12:36 PM, Daniel Dunbar via swift-dev > wrote: > > Anyone know what is up with this Linux test failure? We keep seeing it block > @swift-ci merges: > Failing Tests (1): > Swift :: > compiler_crashers/28279-swift-archetypebuilder-potentialarchetype-getnestedtype.swift

Re: [swift-dev] [Swift CI][OS X] Test failures

Thanks Jordan! Now we have one more test failure left. (Swift :: Reflection/existentials.swift) >>> Second test failure “Swift :: Reflection/existentials.swift” was introduced >>> after following commits: >>> >>> >>> SILGen: Contextualize parameter types in foreign-to-native thunks. — jgroff

[swift-dev] Linux test failure

Anyone know what is up with this Linux test failure? We keep seeing it block @swift-ci merges: Failing Tests (1): Swift :: compiler_crashers/28279-swift-archetypebuilder-potentialarchetype-getnestedtype.swift - Daniel ___ swift-dev mailing list s

Re: [swift-dev] [Swift CI][OS X] Test failures

Fixed in 8cfbf25. Jordan > On May 5, 2016, at 11:44, Jordan Rose wrote: > > Looking into the driver failure. > > >> On May 5, 2016, at 11:08, Mishal Shah via swift-dev > > wrote: >> >> Two tests failing in master branch and its blocking from building toolchain. >

Re: [swift-dev] [Swift CI][OS X] Test failures

Looking into the driver failure. > On May 5, 2016, at 11:08, Mishal Shah via swift-dev > wrote: > > Two tests failing in master branch and its blocking from building toolchain. > > https://ci.swift.org/job/oss-swift-package-osx/ > > > First

[swift-dev] [Swift CI][OS X] Test failures

Two tests failing in master branch and its blocking from building toolchain. https://ci.swift.org/job/oss-swift-package-osx/ First test failure “Swift :: Driver/static-stdlib.swift” was introduced after following commits: Make misc/measure.py compatible with python3 — zyouhousikaku

Re: [swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 15.10 (master) #1207

Hi Todd, We are working on resolving this error. Thanks, Mishal Shah > On May 5, 2016, at 10:34 AM, Todd Fiala wrote: > > -- scp code sign tar -- > WARNING: Your password has expired. > Password change required but no TTY available. > Build step 'Execute shell' marked build as failure > [BFA]

Re: [swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 15.10 (master) #1207

-- scp code sign tar -- WARNING: Your password has expired. Password change required but no TTY available. Build step 'Execute shell' marked build as failure [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s Email was triggered for: Failure - Any Sending email fo

Re: [swift-dev] Building SwiftPM with Foundation

I performed an strace while running the build. Once it starts looking for libFoundation.so it only searches the build location inside the swift directory, but none of the provided -Xlinker paths. 10795 execve("/swiftpm-linux-x86_64/debug/swift-build-stage1", [""..., "-Xlinker", "-rpath", "-Xlin

Re: [swift-dev] Building SwiftPM with Foundation

What you will need to do to make this work is to get the "fake toolchain" to look like how an actual toolchain looks on disk (e.g., libFoundation in the same relative position, in `/../lib/swift/linux`), presumably using a symlink. The special rpath is what is causing the built swift-build (in t

[swift-dev] Building SwiftPM with Foundation

For SwiftPM, I'm looking to replace some POSIX calls with Foundation. NSTask and NSFileManager amongst others. I've created a few PRs already for this, see [1]. However before these can be merged, the build scripts need to be adjusted to allow SwiftPM to build against Foundation. There has alread