libgcc12 @12.3.0: Fails to build on Ventura 13.3.1 (a)

[lukaso (Lukas Oberhuber)]

libgcc12 @12.3.0 (lang)
Variants: [+]stdlib_flag, universal

Build is failing when calling

sudo port install libgcc12

There appears to be something wrong with how the MacOS SDK is being found.

I've configured so that: macosx_deployment_target 11.0 and macosx_sdk_version 11.3 as well as -x11 +no_x11 +quartz +python310 -python27 +no_gnome -gnome -gfortran +debug

[lukaso (Lukas Oberhuber)]

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/main.log

[lukaso (Lukas Oberhuber)]

I've created this patch. However, it's a bit hard to know if my fix is universally applicable. For sure the compile is now working on my machine: ​https://github.com/macports/macports-ports/pull/18676

[mouse07410 (Mouse)]

There appears to be something wrong with how the MacOS SDK is being found.

I personally find this problem rather persistent, with the answer for most if not all of my cases - looking for MacOSX.sdk rather than MacOSXnn.sdk (or even worse, MacOSXnn.m.sdk).

[kencu (Ken)]

Replying to mouse07410:

I personally find this problem rather persistent, with the answer for most if not all of my cases - looking for MacOSX.sdk rather than MacOSXnn.sdk (or even worse, MacOSXnn.m.sdk).

Hey, you're in luck then, because that is exactly what MacPorts does too - at least since I brought the fix in, in Jan 2021!

changeset:e8866c5019d60832527850b4e50fdc1de8878716/macports-ports

Now -- things get screwed around with, accidentally or on purpose, and need to be brought back into line, so if you see a new way this fix needs improving, volunteer away! But the basic idea is alway going to be the same.