Re: Disabling universal on Mojave

2018-09-30 Thread Ryan Schmidt
On Sep 30, 2018, at 15:07, Jack Howarth wrote: > Why aren't we leveraging the -DLIBOMP_OSX_ARCHITECTURES cmake flag to control > whether "x86_64;i386" or "x86_64" get built? We already use CMAKE_OSX_ARCHITECTURES, via the cmake portgroup. The specific problem for libomp was that the portfile

Re: Disabling universal on Mojave

2018-09-30 Thread Jack Howarth
Why aren't we leveraging the -DLIBOMP_OSX_ARCHITECTURES cmake flag to control whether "x86_64;i386" or "x86_64" get built? Jack On Sun, Sep 30, 2018 at 8:03 AM Perry E. Metzger wrote: > On Sun, 30 Sep 2018 00:15:09 -0500 Ryan Schmidt > wrote: > > On Sep 29, 2018, at 08:13, Perry E. M

Re: Disabling universal on Mojave

2018-09-30 Thread Perry E. Metzger
On Sun, 30 Sep 2018 00:15:09 -0500 Ryan Schmidt wrote: > On Sep 29, 2018, at 08:13, Perry E. Metzger wrote: > > > It's relatively important that > > https://github.com/macports/macports-base/pull/107 > > get dealt with relatively soon. There are significant ports that > > fail to build for Mojave

Re: Disabling universal on Mojave

2018-09-29 Thread Ryan Schmidt
On Sep 29, 2018, at 08:13, Perry E. Metzger wrote: > It's relatively important that > https://github.com/macports/macports-base/pull/107 > get dealt with relatively soon. There are significant ports that fail > to build for Mojave because universal builds fail. Can you give an example? > If