Interesting idea to attempt coax Mojave to build for 32-bit. However, I find when I stray from conventional installations to custom, even when I take detailed notes, over time I forget what I did, and it becomes an issue when recreating an installation.
I'm not sure "need" is accurate, but I'd like to have basiliskii and sheepshaver to possibly support a personal journey with Apple 68k hardware. While qemu appears to be moving towards full 68k support, afaik the only way to emulate the old systems in qemu is with a binary alpha release, qemu-system-m68k. As soon as qemu supports mac 68k emulation in general release, and is available through macports, I can return to Mojave or Catalina, as Apple's ban on 32-bit shouldn't reach into emulator guests. > On Nov 21, 2021, at 11:15, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Nov 21, 2021, at 10:08, Chilli wrote: > >> The reason I chose Mojave was because it is the last macOS to support >> running 32-bit applications, but obviously my research was not deep enough. >> Since it can not build 32-bit applications... looks like I'll be backing up >> the Mojave install and replacing wih High Sierra. > > With considerable effort, you may be able to build 32-bit software on Mojave. > The trick may have been to force MacPorts to use the 10.13 SDK, or it may > have involved installing the OS headers into /usr/include using the hidden > installer pkg. There is some information floating around somewhere in the > MacPorts archives about this. However MacPorts base wasn't designed to > accommodate 32-bit building on 10.14 so it may be more trouble than it's > worth. I myself stayed on High Sierra until recently to be able to continue > to build 32-bit software. However the inconvenience of the Let's Encrypt > former root certificate expiring has compelled me to leave 32-bit software > behind and upgrade my OS. >
