> On Sep 19, 2018, at 6:35 AM, Vincent Habchi <[email protected]> wrote:
>
>>> One specific change in Mojave is the deprecation of 32-bit software. Mojave
>>> can run existing 32-bit software but can't build 32-bit software anymore
>>> [3] so MacPorts can't offer 32-bit software on Mojave.
>> I don't need it, but out of curiosity, what exactely isn't provided by Apple
>> that prevents building 32-bits software?
>> Why is it not possible to build 32-bit software with a Macports version of
>> gcc, linked against Macports version of libraries?
>
> The 10.14 SDK doesn’t embed the 32-bit libraries anymore. I suppose if you
> compile clang/llvm from MacPorts, you can still continue to develop i386
> software, though access to Cocoa would be problematic.
Using Macports clang/llvm seems like a good idea to solve the 32-bit issue for
ports like Wine. If the port is Cocoa based, then it would be able to build as
64-bit only anyway.
