[MacPorts] #70641: libgcc14 (libgcc14-14.2.0_1+stdlib_flag.darwin_24.arm64.tbz2) failed to build with config error ("configure: error: cannot compute suffix of object files: cannot compile") on macOS Sequoia beta 15.0 Beta (24A5327a)

[MacPorts]

#70641: libgcc14 (libgcc14-14.2.0_1+stdlib_flag.darwin_24.arm64.tbz2) failed to
build with config error ("configure: error: cannot compute suffix of object
files: cannot compile") on macOS Sequoia beta 15.0 Beta (24A5327a)
-----------------------------+---------------------
  Reporter:  avisformosa     |      Owner:  (none)
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.10.1
Resolution:                  |   Keywords:  sequoia
      Port:  libgcc14 gcc14  |
-----------------------------+---------------------

Comment (by markmentovai):

 Replying to [comment:43 reneeotten]:
 > @cjones051073 @markmentovai it's not completely clear to me from the
 discussion above whether this is supposed to fix the builds. If so, it
 doesn't for me on
 > {{{
 > macOS 15.0 24A335 x86_64
 > Xcode 16.0 16A242d
 > }}}

 This bug, as filed, about this error:

 {{{
 configure: error: cannot compute suffix of object files: cannot compile
 }}}

 is fixed for gcc14 as of [https://github.com/macports/macports-
 ports/commit/048f899dce5faab37c01ced3294fbdf74ede4f03 048f899dce5f], and
 is now fixed on the gcc trunk at
 [https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=33ccc1314dcdb0b988a9276ca6b6ce9b07bea21e
 gcc 33ccc1314dcd]. That’s sufficient to make gcc14 build and work properly
 on mac-arm64 with Xcode 16.

 There’s a separate problem, which is not what this bug was originally
 filed about, concerning a handful of libunwind symbols
 (`__{,de}register_frame_{info,table}*`) that are no longer available in
 macOS 15 or the macOS 15 SDK in Xcode 16. These are only a factor in the
 gcc build on mac-x86_64.

 The situation right now is that gcc14 builds and works on mac-arm64, but
 is still broken on mac-x86_64. This is true for macOS 15, and also for
 macOS 14 using Xcode 16.

 I have no opinion on whether the libunwind problem should be dealt with
 under this bug, or a new bug should be filed. But I’m aware of the problem
 and intend to deal with it either way.

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