Ok, thanks. If I see another one in the next day or two, I’ll just add gcc12 and libgcc12 to my do-not-update list (which if non-empty, is used to generate “and not \( line1 or line2 … \)” to append to a "port upgrade outdated" command). Since my update procedures are halfway between manual and automatic (issuing the initial commands and leaving me to deal interactively with oddities if any, rather than notifying me after-the-fact) for two non-windows batches (22 systems first batch, 4 systems 2nd batch - don’t want too many VMs on any given host running at once), that’s the least ugly thing for me to do, provided I remember to take those entries out when things stabilize.
> On Jul 21, 2022, at 5:20 AM, Chris Jones <[email protected]> wrote: > > > Gcc12 brought a number of issues, that took time to be solved and required a > number of updates in other gcc versions as well, and only became apparent as > users submitted tickets etc. for those issues as they where found. I > apologies for the number of updates, but I think now, touch wood, things will > stabilize. > > If you want to avoid having to build from source large updates, just hold off > doing them until you see the binary tarballs are available, e.g. at > > https://packages.macports.org/gcc12/ > > Chris > > On 21/07/2022 10:12 am, Richard L. Hamilton wrote: >> It seems there have been updates for one version or multiple versions of gcc >> or their libraries nearly every day lately. What’s up with that? >> If one has to recompile (some are prebuilt, thankfully), that REALLY slows >> down updates. With 7 systems (4 of which are VMs at different macOS >> versions), anything that makes updates slower is not fun. Not to mention >> about 22 Linux, Solaris, or Windows systems (mostly VMs/LDOMs/zones, not >> physical boxes! not nearly as much hardware as it sounds like) getting >> updated too. (nostalgia for decades of being in IT, and that doesn’t even >> count emulators for Apollo workstation, IBM mainframe, and other exotica >> distantly remembered) >
