Re: [swift-corelibs-dev] Query on NSLog

2016-07-06 Thread Chris Bailey via swift-corelibs-dev 
The Darwin overlay contains:

https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/Foundation.swift#L918
:
public func NSLog(_ format: String, _ args: CVarArg...) {
  withVaList(args) { NSLogv(format, $0) }
}

So for consistency it would make sense to expose it on other platforms as 
well.

Chris




From:   Tony Parker via swift-corelibs-dev 
To: Luke Howard 
Cc: swift-corelibs-dev@swift.org
Date:   06/07/2016 00:57
Subject:Re: [swift-corelibs-dev] Query on NSLog
Sent by:swift-corelibs-dev-boun...@swift.org



Frankly, I think I just forgot to put a stub for it when we put out the 
first set of APIs.

- Tony

On Jul 5, 2016, at 4:54 PM, Luke Howard  wrote:

I added NSLog for NSKeyedArchiver so the output formatting would more 
closely match Darwin, but I punted whether to make it public.

On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:

Hi Sai,

Out of curiosity, why NSLog instead of Swift’s print function?

- Tony

On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:

Hi All,
 
Currently NSLog  has only one internal function  NSLog()  which can be 
used only by Foundation classes.Can this be made available as a public API 
?
 
 
Thanks & Regards,
 
Sai Hema,Java L3 Support

___
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

--
www.lukehoward.com
soundcloud.com/lukehoward

___
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

Re: [swift-corelibs-dev] Query on NSLog

2016-07-06 Thread Luke Howard via swift-corelibs-dev 
OK, we should fix the function signature to make it identical then (currently 
it does not take an argument list), and perhaps define NSLogv() as well.

> On 6 Jul 2016, at 8:36 PM, Chris Bailey  wrote:
> 
> The Darwin overlay contains: 
> 
> https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/Foundation.swift#L918
>  
> :
>  
> public func NSLog(_ format: String, _ args: CVarArg...) { 
>   withVaList(args) { NSLogv(format, $0) } 
> } 
> 
> So for consistency it would make sense to expose it on other platforms as 
> well. 
> 
> Chris
> 
> 
> 
> 
> From:Tony Parker via swift-corelibs-dev 
>  
> To:Luke Howard  
> Cc:swift-corelibs-dev@swift.org 
> Date:06/07/2016 00:57 
> Subject:Re: [swift-corelibs-dev] Query on NSLog 
> Sent by:swift-corelibs-dev-boun...@swift.org 
> 
> 
> 
> Frankly, I think I just forgot to put a stub for it when we put out the first 
> set of APIs. 
> 
> - Tony 
> 
> On Jul 5, 2016, at 4:54 PM, Luke Howard  > wrote: 
> 
> I added NSLog for NSKeyedArchiver so the output formatting would more closely 
> match Darwin, but I punted whether to make it public. 
> 
> On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev 
> mailto:swift-corelibs-dev@swift.org>> wrote: 
> 
> Hi Sai, 
> 
> Out of curiosity, why NSLog instead of Swift’s print function? 
> 
> - Tony 
> 
> On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev 
> mailto:swift-corelibs-dev@swift.org>> wrote: 
> 
> Hi All, 
>   
> Currently NSLog  has only one internal function  NSLog()  which can be used 
> only by Foundation classes.Can this be made available as a public API ? 
>   
>   
> Thanks & Regards, 
>   
> Sai Hema,Java L3 Support 
> 
> ___
> 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 
>  
> 
> -- 
> www.lukehoward.com 
> soundcloud.com/lukehoward  
> 
> ___
> swift-corelibs-dev mailing list
> swift-corelibs-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev 
> 
> 
> 

--
www.lukehoward.com
soundcloud.com/lukehoward

___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Re: [swift-corelibs-dev] Query on NSLog

2016-07-06 Thread Chris Bailey via swift-corelibs-dev 
Agreed - being consistent is key. The Foundation Reference currently 
documents the Swift API for NSLogv() as:

https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Miscellaneous/Foundation_Functions/#//apple_ref/c/func/NSLogv
func NSLogv(_ format: String, _ args: CVaListPointer)

If that's still correct, then I guess that's what we should be adding

Chris




From:   Luke Howard 
To: Chris Bailey/UK/IBM@IBMGB
Cc: Tony Parker , 
swift-corelibs-dev@swift.org
Date:   06/07/2016 12:31
Subject:Re: [swift-corelibs-dev] Query on NSLog



OK, we should fix the function signature to make it identical then 
(currently it does not take an argument list), and perhaps define NSLogv() 
as well.

On 6 Jul 2016, at 8:36 PM, Chris Bailey  wrote:

The Darwin overlay contains: 

https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/Foundation.swift#L918
: 
public func NSLog(_ format: String, _ args: CVarArg...) { 
  withVaList(args) { NSLogv(format, $0) } 
} 

So for consistency it would make sense to expose it on other platforms as 
well. 

Chris




From:Tony Parker via swift-corelibs-dev <
swift-corelibs-dev@swift.org> 
To:Luke Howard  
Cc:swift-corelibs-dev@swift.org 
Date:06/07/2016 00:57 
Subject:Re: [swift-corelibs-dev] Query on NSLog 
Sent by:swift-corelibs-dev-boun...@swift.org 



Frankly, I think I just forgot to put a stub for it when we put out the 
first set of APIs. 

- Tony 

On Jul 5, 2016, at 4:54 PM, Luke Howard  wrote: 

I added NSLog for NSKeyedArchiver so the output formatting would more 
closely match Darwin, but I punted whether to make it public. 

On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote: 

Hi Sai, 

Out of curiosity, why NSLog instead of Swift’s print function? 

- Tony 

On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote: 

Hi All, 
  
Currently NSLog  has only one internal function  NSLog()  which can be 
used only by Foundation classes.Can this be made available as a public API 
? 
  
  
Thanks & Regards, 
  
Sai Hema,Java L3 Support 

___
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 

-- 
www.lukehoward.com
soundcloud.com/lukehoward 

___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev



--
www.lukehoward.com
soundcloud.com/lukehoward



___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

[swift-corelibs-dev] Troubleshooting libdispatch build failure

2016-07-06 Thread Jean-Pierre Simard via swift-corelibs-dev 
Up until a few days ago, running 'util/build-script --libdispatch'
completed successfully.

Now it fails, generating the following errors. Any ideas on how to resolve
these? Or other ways people are using to build libdispatch at the moment?
Thanks!

/bin/bash ../libtool  --tag=CXX   --mode=compile
/build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++ -DHAVE_CONFIG_H -I.
-I//swift-corelibs-libdispatch/src -I../config  -I..
-I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
-DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
-fvisibility=hidden -momit-leaf-frame-pointer  -I/usr/include/kqueue
-isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
-fno-exceptions -g -O2 -c -o swift/libdispatch_la-DispatchStubs.lo `test -f
'swift/DispatchStubs.cc' || echo
'//swift-corelibs-libdispatch/src/'`swift/DispatchStubs.cc
libtool: compile:  /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++
-DHAVE_CONFIG_H -I. -I//swift-corelibs-libdispatch/src -I../config -I..
-I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
-DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
-fvisibility=hidden -momit-leaf-frame-pointer -I/usr/include/kqueue
-isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
-fno-exceptions -g -O2 -c
//swift-corelibs-libdispatch/src/swift/DispatchStubs.cc  -fPIC -DPIC -o
swift/.libs/libdispatch_la-DispatchStubs.o
/build/Ninja-DebugAssert/swift-linux-x86_64/bin/swiftc -frontend -c
//swift-corelibs-libdispatch/src/swift/Block.swift
//swift-corelibs-libdispatch/src/swift/Data.swift
//swift-corelibs-libdispatch/src/swift/Dispatch.swift
//swift-corelibs-libdispatch/src/swift/IO.swift
//swift-corelibs-libdispatch/src/swift/Private.swift
//swift-corelibs-libdispatch/src/swift/Queue.swift
//swift-corelibs-libdispatch/src/swift/Source.swift
//swift-corelibs-libdispatch/src/swift/Time.swift
//swift-corelibs-libdispatch/src/swift/Wrapper.swift -primary-file
//swift-corelibs-libdispatch/src/swift/Block.swift \
-Xcc
-fmodule-map-file=//swift-corelibs-libdispatch/dispatch/module.modulemap
-I//swift-corelibs-libdispatch -Xcc -fblocks -module-name Dispatch
-module-link-name dispatch \
-o /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o
-emit-module-path
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftmodule
\
-emit-module-doc-path
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftdoc
-emit-dependencies-path
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.d \
-emit-reference-dependencies-path
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.swiftdeps
\
-module-cache-path ..
:1:10: note: in file included from :1:
#include "dispatch.h"
 ^
//swift-corelibs-libdispatch/dispatch/dispatch.h:99:10: error:
'os/object.h' file not found
#include 
 ^
//swift-corelibs-libdispatch/src/swift/Block.swift:13:8: error: could not
build Objective-C module 'CDispatch'
import CDispatch
   ^
Makefile:956: recipe for target
'/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o' failed
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Re: [swift-corelibs-dev] Troubleshooting libdispatch build failure

2016-07-06 Thread David P Grove via swift-corelibs-dev 

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
would help?

--dave



From:   Jean-Pierre Simard 
To: swift-corelibs-dev@swift.org
Cc: David P Grove/Watson/IBM@IBMUS
Date:   07/06/2016 04:28 PM
Subject:Troubleshooting libdispatch build failure



Up until a few days ago, running 'util/build-script --libdispatch'
completed successfully.

Now it fails, generating the following errors. Any ideas on how to resolve
these? Or other ways people are using to build libdispatch at the moment?
Thanks!

/bin/bash ../libtool  --tag=CXX
--mode=compile /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++
-DHAVE_CONFIG_H -I. -I//swift-corelibs-libdispatch/src -I../config  -I..
-I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
-DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
-fvisibility=hidden -momit-leaf-frame-pointer  -I/usr/include/kqueue
-isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
-fno-exceptions -g -O2 -c -o swift/libdispatch_la-DispatchStubs.lo `test -f
'swift/DispatchStubs.cc' || echo
'//swift-corelibs-libdispatch/src/'`swift/DispatchStubs.cc
libtool: compile:  /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++
-DHAVE_CONFIG_H -I. -I//swift-corelibs-libdispatch/src -I../config -I..
-I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
-DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
-fvisibility=hidden -momit-leaf-frame-pointer -I/usr/include/kqueue
-isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
-fno-exceptions -g -O2
-c //swift-corelibs-libdispatch/src/swift/DispatchStubs.cc  -fPIC -DPIC -o
swift/.libs/libdispatch_la-DispatchStubs.o
/build/Ninja-DebugAssert/swift-linux-x86_64/bin/swiftc -frontend
-c //swift-corelibs-libdispatch/src/swift/Block.swift 
//swift-corelibs-libdispatch/src/swift/Data.swift 
//swift-corelibs-libdispatch/src/swift/Dispatch.swift 
//swift-corelibs-libdispatch/src/swift/IO.swift 
//swift-corelibs-libdispatch/src/swift/Private.swift 
//swift-corelibs-libdispatch/src/swift/Queue.swift 
//swift-corelibs-libdispatch/src/swift/Source.swift 
//swift-corelibs-libdispatch/src/swift/Time.swift 
//swift-corelibs-libdispatch/src/swift/Wrapper.swift
 -primary-file //swift-corelibs-libdispatch/src/swift/Block.swift \
-Xcc
-fmodule-map-file=//swift-corelibs-libdispatch/dispatch/module.modulemap
-I//swift-corelibs-libdispatch -Xcc -fblocks -module-name Dispatch
-module-link-name dispatch \
-o /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o
-emit-module-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftmodule
 \
-emit-module-doc-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftdoc

-emit-dependencies-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.d
 \
-emit-reference-dependencies-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.swiftdeps
 \
-module-cache-path ..
:1:10: note: in file included from :1:
#include "dispatch.h"
         ^
//swift-corelibs-libdispatch/dispatch/dispatch.h:99:10: error:
'os/object.h' file not found
#include 
         ^
//swift-corelibs-libdispatch/src/swift/Block.swift:13:8: error: could not
build Objective-C module 'CDispatch'
import CDispatch
       ^
Makefile:956: recipe for target
'/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o'
failed


___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Re: [swift-corelibs-dev] Troubleshooting libdispatch build failure

2016-07-06 Thread Jean-Pierre Simard via swift-corelibs-dev 
Thanks for getting back to me so quickly Dave.

This worked last week, but didn't yesterday when I tried again. My "last
few days" guess might actually just be since yesterday morning. Maybe
something's changed since your last checkouts from yesterday morning?
Running these commands on a fresh Ubuntu 16.04 machine (i.e. no build
cache) gives me the output I shared above.

apt-get update && \
apt-get install -y \
  autoconf \
  clang \
  cmake \
  git \
  icu-devtools \
  libblocksruntime-dev \
  libbsd-dev \
  libedit-dev \
  libicu-dev \
  libkqueue-dev \
  libncurses5-dev \
  libpython-dev \
  libsqlite3-dev \
  libtool \
  libxml2-dev \
  ninja-build \
  pkg-config \
  python \
  swig \
  uuid-dev
git clone https://github.com/apple/swift.git
cd swift
utils/update-checkout --clone
utils/build-script --libdispatch

I suspect that the Xcode 8 beta 2 set of changes that landed yesterday may
have caused this. There were patches on all sorts of repos (swift-llvm,
swift-clang, swift, etc).

On Wed, Jul 6, 2016 at 4:52 PM, David P Grove  wrote:

> 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 would
> help?
>
> --dave
>
> [image: Inactive hide details for Jean-Pierre Simard ---07/06/2016
> 04:28:46 PM---Up until a few days ago, running 'util/build-script 
> --]Jean-Pierre
> Simard ---07/06/2016 04:28:46 PM---Up until a few days ago, running
> 'util/build-script --libdispatch' completed successfully.
>
> From: Jean-Pierre Simard 
> To: swift-corelibs-dev@swift.org
> Cc: David P Grove/Watson/IBM@IBMUS
> Date: 07/06/2016 04:28 PM
> Subject: Troubleshooting libdispatch build failure
> --
>
>
>
> Up until a few days ago, running 'util/build-script --libdispatch'
> completed successfully.
>
> Now it fails, generating the following errors. Any ideas on how to resolve
> these? Or other ways people are using to build libdispatch at the moment?
> Thanks!
>
> /bin/bash ../libtool  --tag=CXX   --mode=compile
> /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++ -DHAVE_CONFIG_H -I.
> -I//swift-corelibs-libdispatch/src -I../config  -I..
> -I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
> -DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
> -fvisibility=hidden -momit-leaf-frame-pointer  -I/usr/include/kqueue
> -isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
> -fno-exceptions -g -O2 -c -o swift/libdispatch_la-DispatchStubs.lo `test -f
> 'swift/DispatchStubs.cc' || echo
> '//swift-corelibs-libdispatch/src/'`swift/DispatchStubs.cc
> libtool: compile:  /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++
> -DHAVE_CONFIG_H -I. -I//swift-corelibs-libdispatch/src -I../config -I..
> -I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
> -DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
> -fvisibility=hidden -momit-leaf-frame-pointer -I/usr/include/kqueue
> -isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
> -fno-exceptions -g -O2 -c
> //swift-corelibs-libdispatch/src/swift/DispatchStubs.cc  -fPIC -DPIC -o
> swift/.libs/libdispatch_la-DispatchStubs.o
> /build/Ninja-DebugAssert/swift-linux-x86_64/bin/swiftc -frontend -c
> //swift-corelibs-libdispatch/src/swift/Block.swift
> //swift-corelibs-libdispatch/src/swift/Data.swift
> //swift-corelibs-libdispatch/src/swift/Dispatch.swift
> //swift-corelibs-libdispatch/src/swift/IO.swift
> //swift-corelibs-libdispatch/src/swift/Private.swift
> //swift-corelibs-libdispatch/src/swift/Queue.swift
> //swift-corelibs-libdispatch/src/swift/Source.swift
> //swift-corelibs-libdispatch/src/swift/Time.swift
> //swift-corelibs-libdispatch/src/swift/Wrapper.swift -primary-file
> //swift-corelibs-libdispatch/src/swift/Block.swift \
> -Xcc
> -fmodule-map-file=//swift-corelibs-libdispatch/dispatch/module.modulemap
> -I//swift-corelibs-libdispatch -Xcc -fblocks -module-name Dispatch
> -module-link-name dispatch \
> -o /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o
> -emit-module-path
> /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftmodule
> \
> -emit-module-doc-path
> /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftdoc
> -emit-dependencies-path
> /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.d \
> -emit-reference-dependencies-path
> /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.swiftdeps
> \
> -module-cache-path ..
> :1:10: note: in file included from :1:
> #include "dispatch.h"
>  ^
> //swift-corelibs-libdispatch/dispatch/dispatch.h:99:10: error:
> 'os/object.h' file not found
> #include 
>

Re: [swift-corelibs-dev] Troubleshooting libdispatch build failure

2016-07-06 Thread David P Grove via swift-corelibs-dev 

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 failure



Thanks for getting back to me so quickly Dave.

This worked last week, but didn't yesterday when I tried again. My "last
few days" guess might actually just be since yesterday morning. Maybe
something's changed since your last checkouts from yesterday morning?
Running these commands on a fresh Ubuntu 16.04 machine (i.e. no build
cache) gives me the output I shared above.

apt-get update && \
    apt-get install -y \
      autoconf \
      clang \
      cmake \
      git \
      icu-devtools \
      libblocksruntime-dev \
      libbsd-dev \
      libedit-dev \
      libicu-dev \
      libkqueue-dev \
      libncurses5-dev \
      libpython-dev \
      libsqlite3-dev \
      libtool \
      libxml2-dev \
      ninja-build \
      pkg-config \
      python \
      swig \
      uuid-dev
git clone https://github.com/apple/swift.git
cd swift
utils/update-checkout --clone
utils/build-script --libdispatch

I suspect that the Xcode 8 beta 2 set of changes that landed yesterday may
have caused this. There were patches on all sorts of repos (swift-llvm,
swift-clang, swift, etc).

On Wed, Jul 6, 2016 at 4:52 PM, David P Grove  wrote:
  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 would
  help?

  --dave

  Inactive hide details for Jean-Pierre Simard ---07/06/2016 04:28:46
  PM---Up until a few days ago, running 'util/build-script --Jean-Pierre
  Simard ---07/06/2016 04:28:46 PM---Up until a few days ago, running
  'util/build-script --libdispatch' completed successfully.

  From: Jean-Pierre Simard 
  To: swift-corelibs-dev@swift.org
  Cc: David P Grove/Watson/IBM@IBMUS
  Date: 07/06/2016 04:28 PM
  Subject: Troubleshooting libdispatch build failure




  Up until a few days ago, running 'util/build-script --libdispatch'
  completed successfully.

  Now it fails, generating the following errors. Any ideas on how to
  resolve these? Or other ways people are using to build libdispatch at the
  moment? Thanks!

  /bin/bash ../libtool  --tag=CXX
  --mode=compile /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++
  -DHAVE_CONFIG_H -I. -I//swift-corelibs-libdispatch/src -I../config  -I..
  -I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
  -DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include
  -Wall -fvisibility=hidden -momit-leaf-frame-pointer
  -I/usr/include/kqueue -isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks
  -std=gnu++11 -fno-exceptions -g -O2 -c -o
  swift/libdispatch_la-DispatchStubs.lo `test -f 'swift/DispatchStubs.cc'
  || echo '//swift-corelibs-libdispatch/src/'`swift/DispatchStubs.cc
  libtool: compile:  /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++
  -DHAVE_CONFIG_H -I. -I//swift-corelibs-libdispatch/src -I../config -I..
  -I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
  -DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include
  -Wall -fvisibility=hidden -momit-leaf-frame-pointer -I/usr/include/kqueue
  -isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
  -fno-exceptions -g -O2
  -c //swift-corelibs-libdispatch/src/swift/DispatchStubs.cc  -fPIC -DPIC
  -o swift/.libs/libdispatch_la-DispatchStubs.o
  /build/Ninja-DebugAssert/swift-linux-x86_64/bin/swiftc -frontend
  -c //swift-corelibs-libdispatch/src/swift/Block.swift 
//swift-corelibs-libdispatch/src/swift/Data.swift 
//swift-corelibs-libdispatch/src/swift/Dispatch.swift 
//swift-corelibs-libdispatch/src/swift/IO.swift 
//swift-corelibs-libdispatch/src/swift/Private.swift 
//swift-corelibs-libdispatch/src/swift/Queue.swift 
//swift-corelibs-libdispatch/src/swift/Source.swift 
//swift-corelibs-libdispatch/src/swift/Time.swift 
//swift-corelibs-libdispatch/src/swift/Wrapper.swift
 -primary-file //swift-corelibs-libdispatch/src/swift/Block.swift \
  -Xcc
  -fmodule-map-file=//swift-corelibs-libdispatch/dispatch/module.modulemap
  -I//swift-corelibs-libdispatch -Xcc -fblocks -module-name Dispatch
  -module-link-name dispatch \
  -o /build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o
  -emit-module-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftmodule
 \
  -emit-module-doc-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.~partial.swiftdoc
 -emit-dependencies-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src/swift/Block.o.d
 \
  -emit-reference-dependencies-path 
/build/Ninja-DebugAssert/libdispatch-linux-x86_64/src

Re: [swift-corelibs-dev] Troubleshooting libdispatch build failure

2016-07-06 Thread Jean-Pierre Simard via swift-corelibs-dev 
That's it. I managed to build things again by checking out everything at
the state it was yesterday morning:

for dir in */; do
  cd $dir; git checkout `git rev-list -n 1 --before="2016-07-05 08:00"
master`; cd ..;
done

Still don't know which change(s) are responsible though.

On Wed, Jul 6, 2016 at 8:09 PM, David P Grove  wrote:

> ok, thanks for the details.
>
> I'll grab the latest myself tomorrow morning and see if I can reproduce.
>
> --dave
>
> [image: Inactive hide details for Jean-Pierre Simard ---07/06/2016
> 06:21:03 PM---Thanks for getting back to me so quickly Dave. This 
> wo]Jean-Pierre
> Simard ---07/06/2016 06:21:03 PM---Thanks for getting back to me so quickly
> Dave. This worked last week, but didn't yesterday when I tr
>
> 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 failure
>
> --
>
>
>
> Thanks for getting back to me so quickly Dave.
>
> This worked last week, but didn't yesterday when I tried again. My "last
> few days" guess might actually just be since yesterday morning. Maybe
> something's changed since your last checkouts from yesterday morning?
> Running these commands on a fresh Ubuntu 16.04 machine (i.e. no build
> cache) gives me the output I shared above.
>
> apt-get update && \
> apt-get install -y \
>   autoconf \
>   clang \
>   cmake \
>   git \
>   icu-devtools \
>   libblocksruntime-dev \
>   libbsd-dev \
>   libedit-dev \
>   libicu-dev \
>   libkqueue-dev \
>   libncurses5-dev \
>   libpython-dev \
>   libsqlite3-dev \
>   libtool \
>   libxml2-dev \
>   ninja-build \
>   pkg-config \
>   python \
>   swig \
>   uuid-dev
> git clone *https://github.com/apple/swift.git*
> 
> cd swift
> utils/update-checkout --clone
> utils/build-script --libdispatch
>
> I suspect that the Xcode 8 beta 2 set of changes that landed yesterday may
> have caused this. There were patches on all sorts of repos (swift-llvm,
> swift-clang, swift, etc).
>
> On Wed, Jul 6, 2016 at 4:52 PM, David P Grove <*gro...@us.ibm.com*
> > wrote:
>
>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
>would help?
>
>--dave
>
>[image: Inactive hide details for Jean-Pierre Simard ---07/06/2016
>04:28:46 PM---Up until a few days ago, running 'util/build-script 
> --]Jean-Pierre
>Simard ---07/06/2016 04:28:46 PM---Up until a few days ago, running
>'util/build-script --libdispatch' completed successfully.
>
>From: Jean-Pierre Simard <*j...@jpsim.com* >
>To: *swift-corelibs-dev@swift.org* 
>Cc: David P Grove/Watson/IBM@IBMUS
>Date: 07/06/2016 04:28 PM
>Subject: Troubleshooting libdispatch build failure
>--
>
>
>
>
>Up until a few days ago, running 'util/build-script --libdispatch'
>completed successfully.
>
>Now it fails, generating the following errors. Any ideas on how to
>resolve these? Or other ways people are using to build libdispatch at the
>moment? Thanks!
>
>/bin/bash ../libtool  --tag=CXX   --mode=compile
>/build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++ -DHAVE_CONFIG_H -I.
>-I//swift-corelibs-libdispatch/src -I../config  -I..
>-I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
>-DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
>-fvisibility=hidden -momit-leaf-frame-pointer  -I/usr/include/kqueue
>-isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
>-fno-exceptions -g -O2 -c -o swift/libdispatch_la-DispatchStubs.lo `test -f
>'swift/DispatchStubs.cc' || echo
>'//swift-corelibs-libdispatch/src/'`swift/DispatchStubs.cc
>libtool: compile:
> /build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang++ -DHAVE_CONFIG_H -I.
>-I//swift-corelibs-libdispatch/src -I../config -I..
>-I//swift-corelibs-libdispatch -I//swift-corelibs-libdispatch/private
>-DDISPATCH_USE_DTRACE=0 -I//swift-corelibs-libdispatch/libpwq/include -Wall
>-fvisibility=hidden -momit-leaf-frame-pointer -I/usr/include/kqueue
>-isystem /usr/include/bsd -DLIBBSD_OVERLAY -fblocks -std=gnu++11
>-fno-exceptions -g -O2 -c
>//swift-corelibs-libdispatch/src/swift/DispatchStubs.cc  -fPIC -DPIC -o
>swift/.libs/libdispatch_la-DispatchStubs.o
>/build/Ninja-DebugAssert/swift-linux-x86_64/bin/swiftc -frontend -c
>//swift-corelibs-libdispatch/src/swift/Block.swift
>//swift-corelibs-libdispatch/src/swift/Data.swift
>//swift-corelibs-libdispatch/src/swift/Dispatch.swift
>//swift-corel