[MacPorts] #70328: libgcc14 @14.1.0_0+stdlib_flag: Can't build against 11.3 SDK on macOS 14

[MacPorts]

#70328: libgcc14 @14.1.0_0+stdlib_flag: Can't build against 11.3 SDK on macOS 14
-----------------------+--------------------
  Reporter:  lukaso    |      Owner:  (none)
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:
      Port:  libgcc14  |
-----------------------+--------------------

Comment (by lukaso):

 > I don't know how you got your MacOSX11 SDK on macOS14, but perhaps you
 did not fully install it correctly and you are missing the equivalent sym
 links above for it. If so fix this and try again.

 Yeah, I fixed that, but it just went to the standard sdk.

 My workaround for now: overlay the port with the function above because
 I've run out of time.

 I'll hopefully have time this weekend.

 Separately: what is the benefit of special casing the SDKs?

 This was done January 2021 for gcc 8, 9 and 10:
 https://github.com/macports/macports-
 ports/commit/e8866c5019d60832527850b4e50fdc1de8878716 by @kencu.

 But other than stating the SDKs change rapidly, there isn't really a
 justification. I'm inferring it has something to do with building with an
 SDK and then baking in that SDK when building with gcc. Looks like there
 is some deep problem in gcc related to cross compiling. Looks like it's
 related to `--with-sdkroot` and `--with-build-sdkroot` or some such.

 This is the linked bug(I haven't fully researched it):
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885

 I think it is supposed to make the gcc forward compatible.

 Hope these ramblings help!

-- 
Ticket URL: <https://trac.macports.org/ticket/70328#comment:26>
MacPorts <https://www.macports.org/>
Ports system for macOS