I also think, having done it, that MacPorts in general will likely never implement it.
Having said that, it was literally 15 minutes of tweaking portconfigure.tcl -- the rest was just build time. Ken > On Nov 4, 2018, at 07:04, Mark Anderson <e...@emer.net> wrote: > > I've just given up on 32-bit on macOS. Wine is the big pain there, but I'm > waiting for upstream to fix it since I don't use it much anyway. > > I think I'm with Chris. This is a lot of effort for something that is going > to break permanently in 10.15+, we should probably just add an error to > things that can only build 32-bit on 10.14 and greater or something, in > preparation for the death of macOS 32-bit. > > Unless, we want to spin up something using Hypervisor.framework to run mach-o > in 32 bit or something. Or wait for that to happen, which I have to imagine > will eventually. > > —Mark > _______________________ > Mark E. Anderson <e...@emer.net> > > >> On Sun, Nov 4, 2018 at 9:44 AM Christopher Jones <jon...@hep.phy.cam.ac.uk> >> wrote: >> >> >> > On 4 Nov 2018, at 1:54 pm, Ryan Schmidt <ryandes...@macports.org> wrote: >> > >> > On Nov 4, 2018, at 01:41, Ken Cunningham wrote: >> >> >> >> I thought I’d try a 32-bit compatible installation of MacPorts today on >> >> Mojave as a proof-of-concept, so I made a new prefix under /opt/universal >> >> and set up macports in it. >> >> >> >> I installed a copy of the MacOSX10.13.sdk and referenced that during the >> >> builds. >> > >> > I thought we decided we didn't want to pursue that idea, based on Joshua's >> > objections, and instead we wanted to figure out a way to compile universal >> > with the 10.14 SDK, maybe by making a universal 10.14 SDK, or maybe by >> > forcing the build to use libsystem.dylib instead of the tbd file as >> > suggested by Jack. >> >> Personally, I am against both ideas. I particularly object to the above as >> IMHO its hacking into the build system in ways Apple clearly does not >> support. >> >> For me, we should just accept 32-bit builds are not possible on Mojave. I’ve >> asked this before but other than wine and its related ports do we loose, >> because they do not, or cannot be made to, work 64 bit. >> >> I don’t get all the effort going into keep 32 bit going for just a little >> bit longer, until Apple completely pull the plug, in a future macOS release. >> >> Chris >> >> > >> > >> >> To make it work, I made a couple of minor mods to portconfigure.tcl >> >> rather than add the same stuff to every portfile. A few ports needed >> >> minor tweaking, but in the end everything built through without any >> >> trouble and wine and other ports work. >> >> >> >> I can post the portconfigure tweaks if anyone is interested. >> >> >> >> Ken >> > >>
