Re: ino64 package fallout

2017-05-25 Thread Konstantin Belousov
On Wed, May 24, 2017 at 05:49:04PM -0700, Don Lewis wrote: > On 24 May, Konstantin Belousov wrote: > > On Wed, May 24, 2017 at 10:05:22AM -0700, Don Lewis wrote: > >> I just upgraded by package build box and its poudriere jail to r318776 > >> and ran into some significant package build fallout. >

Re: ino64 package fallout

2017-05-24 Thread Don Lewis
On 24 May, Konstantin Belousov wrote: > On Wed, May 24, 2017 at 10:05:22AM -0700, Don Lewis wrote: >> I just upgraded by package build box and its poudriere jail to r318776 >> and ran into some significant package build fallout. > > There are several reviews that fix ports with most significant

Re: ino64 package fallout

2017-05-24 Thread Konstantin Belousov
On Wed, May 24, 2017 at 10:05:22AM -0700, Don Lewis wrote: > I just upgraded by package build box and its poudriere jail to r318776 > and ran into some significant package build fallout. There are several reviews that fix ports with most significant fallouts, lang/llvm39

Re: ino64 package fallout

2017-05-24 Thread Shawn Webb
On Wed, May 24, 2017 at 10:05:22AM -0700, Don Lewis wrote: > I just upgraded by package build box and its poudriere jail to r318776 > and ran into some significant package build fallout. > > devel/llvm40:build: > > > /usr/bin/c++ -DHAVE_RPC_XDR_H=0 -DHAVE_TIRPC_RPC_XDR_H=0 -O2 -pipe >

ino64 package fallout

2017-05-24 Thread Don Lewis
I just upgraded by package build box and its poudriere jail to r318776 and ran into some significant package build fallout. devel/llvm40:build: /usr/bin/c++ -DHAVE_RPC_XDR_H=0 -DHAVE_TIRPC_RPC_XDR_H=0 -O2 -pipe -fstack-protector -isystem /usr/local/include -fno-strict-aliasing -isystem