On Thu, Apr 9, 2026 at 7:39 PM Riccardo Mottola <[email protected]> wrote:
> > Do you really need gcc-4.8 and gcc7 after all? Generally everything > > must work with gcc14 (or gcc15, I guess). Of existing ports, > > tenfourfox requires gcc-4.8, but tenfourfox itself is of little > > utility now (and available pre-built if you need it for something > > specific). There are white-star / powerfox which build with modern > > gcc. Aside of that, I cannot recall what may need specifically an old > > non-Apple gcc version. Even if such ports exist, it may be worthwhile > > to fix them to build with modern gcc rather than carrying on > > dependency on the whole zoo of gcc versions. > > If you already have gcc15 via MacPorts, you may just try using that, > > avoiding old versions. And if something fails to build with it, bug > > reports will be useful. > > Well, gcc6/gcc7 are very reliable compilers. I won’t subscribe to this assessment, tbh, since a) I know of specific powerpc bugs which were fixed in recent gcc versions (because I reported them), and b) I can’t recall an instance of a port which builds with gcc7 but cannot build with gcc14. (But this is off-topic, of course; regardless of preferences for a specific compiler, dependencies should work as designed.) > 10.5 has no build bots, on my 32bit and 64bit x86 compilers built. > Did you establish that on ppc MacPorts tries to actually build every libgcc from 15 down to 6? It should not happen, of course, on either arch, and was not designed that way, but I think Ken tested the whole setup when gcc7 was replaced with gcc14, and provisionally it worked fine. Possibly a switch to gcc15 broke something (I decided to skip gcc15 completely, there was nothing to gain with it, so no idea what MacPorts does now).
