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
On Sat, 29 Sep 2018 at 21:39, Gregorio Litenstein wrote:
>
> *feels not-so-subtly called out* hahaha.
On an unrelated note: since I don't know how GitHub works precisely
with notifications, did you see the three comments from Ryan with
requests for other fixes? I would like to ask you to address t
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
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
