Re: Potential problem with small subset of Cocoa ports on Xcode 10

On Sat, 29 Sep 2018 06:30:39 +0100 Chris Jones wrote: > > On 28 Sep 2018, at 10:55 pm, Perry E. Metzger > > wrote: > > > > On Sat, 29 Sep 2018 07:40:22 +1000 Joshua Root > > wrote: > Here's the kludge for a Portfile: > > if {[vercmp ${xcodeversion} 10.0] >= 0} { >

Re: Potential problem with small subset of Cocoa ports on Xcode 10

> On 28 Sep 2018, at 10:55 pm, Perry E. Metzger wrote: > > On Sat, 29 Sep 2018 07:40:22 +1000 Joshua Root > wrote: Here's the kludge for a Portfile: if {[vercmp ${xcodeversion} 10.0] >= 0} { destroot.pre_args -UseNewBuildSystem=NO } Arguably, one

Re: Potential problem with small subset of Cocoa ports on Xcode 10

On Sat, 29 Sep 2018 07:40:22 +1000 Joshua Root wrote: > >> Here's the kludge for a Portfile: > >> > >> if {[vercmp ${xcodeversion} 10.0] >= 0} { > >>destroot.pre_args -UseNewBuildSystem=NO > >> } > >> > >> Arguably, one should do "= 0" rather than ">=" since the bug may > >> be fixed in

Re: Potential problem with small subset of Cocoa ports on Xcode 10

On Fri, 28 Sep 2018 22:20:06 +0100 Chris Jones wrote: > > Arguably, one should do "= 0" rather than ">=" since the bug may > > be fixed in Xcode 10.whatever. > > That would depend on whether you are correct or not in saying its a > bug in Xcode. If it isn’t making it an equality will just mean

Re: Potential problem with small subset of Cocoa ports on Xcode 10

> On 28 Sep 2018, at 8:58 pm, Perry E. Metzger wrote: > > On Fri, 28 Sep 2018 08:22:01 -0500 Marius Schamschula > wrote: >> Perry, >> >> I’ve just run into this problem with TeXShop4. The build phase >> succeeds, but destroot fails. >> >> How does one revert to the “old” build system under

Re: Potential problem with small subset of Cocoa ports on Xcode 10

On 2018-9-29 05:45 , Chris Jones wrote: > > > On 28 Sep 2018, at 2:35 pm, Joshua Root > wrote: > >> On 2018-9-28 23:12 , Perry E. Metzger wrote: >>> Note that the new build system is also much more strict about many >>> things, you may have to clean up latent sloppy

Re: Potential problem with small subset of Cocoa ports on Xcode 10

On Fri, 28 Sep 2018 08:22:01 -0500 Marius Schamschula wrote: > Perry, > > I’ve just run into this problem with TeXShop4. The build phase > succeeds, but destroot fails. > > How does one revert to the “old” build system under Xcode 10? Here's the kludge for a Portfile: if {[vercmp

Re: Potential problem with small subset of Cocoa ports on Xcode 10

On Fri, 28 Sep 2018 23:35:06 +1000 Joshua Root wrote: > On 2018-9-28 23:12 , Perry E. Metzger wrote: > > Note that the new build system is also much more strict about many > > things, you may have to clean up latent sloppy code (like the use > > of for something that should be "include.h" in C)

Re: Potential problem with small subset of Cocoa ports on Xcode 10

Perry, I’ve just run into this problem with TeXShop4. The build phase succeeds, but destroot fails. How does one revert to the “old” build system under Xcode 10? > On Sep 28, 2018, at 8:12 AM, Perry E. Metzger wrote: > > [resending as I messed up the first time...] > > On Fri, 28 Sep 2018

Re: Potential problem with small subset of Cocoa ports on Xcode 10

[resending as I messed up the first time...] On Fri, 28 Sep 2018 00:21:17 -0500 Ryan Schmidt wrote: > On Sep 26, 2018, at 17:14, Perry E. Metzger wrote: > > > It seems that there's a bad interaction between Xcode 10's new > > build system and certain ports. "pinentry-mac" is the only one > >

Re: Potential problem with small subset of Cocoa ports on Xcode 10

On Sep 26, 2018, at 17:14, Perry E. Metzger wrote: > It seems that there's a bad interaction between Xcode 10's new build > system and certain ports. "pinentry-mac" is the only one I've hit so > far but there may be others. The kludge is to tell Xcode 10 (if it is > the version running) to use