On Mon, 29 Oct 2018 at 21:43, Joshua Root wrote:
> On 2018-10-30 06:13 , Mojca Miklavec wrote:
> > That said, I would like it if MacPorts had somewhat better support for
> > compiling binaries targeting older OSes on newer ones, ...
>
> Unfortunately it's mostly not MacPorts that needs the support
On 2018-10-30 06:13 , Mojca Miklavec wrote:
> That said, I would like it if MacPorts had somewhat better support for
> compiling binaries targeting older OSes on newer ones, ...
Unfortunately it's mostly not MacPorts that needs the support but the
individual build systems, most of which have no c
On Mon, 29 Oct 2018 at 07:15, Ken Cunningham wrote:
>
> I notice homebrew is forcing the installation of binaries built on their
> 10.12 or 10.13 builders onto 10.14 to get around the 32bit build problem on
> 10.14.
>
> I don't believe there is any way to force our binary installer to install
>
At the moment, you're right, we don't have anything that can do that. So at the
moment we would need to find a way to compile 32-bit on 10.14. Jack Howarth
mentioned that the system dylib still has 32-bit symbols (of course, so that it
can run 32-bit software) but that the tbd file for the
On Oct 29, 2018, at 01:15, Ken Cunningham wrote:
> I notice homebrew is forcing the installation of binaries built on their
> 10.12 or 10.13 builders onto 10.14 to get around the 32bit build problem on
> 10.14.
>
> I don't believe there is any way to force our binary installer to install
>
I notice homebrew is forcing the installation of binaries built on their 10.12
or 10.13 builders onto 10.14 to get around the 32bit build problem on 10.14.
I don't believe there is any way to force our binary installer to install older
system builds in the same way -- but if there was, it would