[MacPorts] #71423: qt5-qtbase @5.15.15_0: ASSERT failure in QMacVersion: "Could not find any version load command" (was: qt5-qtbase @5.15.15_0 Failed to configure)

[MacPorts]

#71423: qt5-qtbase @5.15.15_0: ASSERT failure in QMacVersion: "Could not find any
version load command"
-------------------------+---------------------------------
  Reporter:  mebius-san  |      Owner:  MarcusCalhoun-Lopez
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:  sequoia arm64
      Port:  qt5-qtbase  |
-------------------------+---------------------------------
Changes (by ryandesign):

 * cc: d7gonzo, jamodeo12 (added)


Comment:

 The error in mebius-san's main.log.zip is:

 {{{
 ASSERT failure in QMacVersion: "Could not find any version load command",
 file
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt5/qt5-qtbase/work
 /qtbase-everywhere-src-5.15.15/src/corelib/kernel/qcore_mac.mm, line 761
 }}}

 This is in the `QMacVersion::versionsForImage` function which is trying
 and failing to parse a Mach-O header. I'm not sure why this fails and
 could not find other results for this error message when I searched for
 it. I looked at the upstream qt repository and did not see any recent
 fixes in this function and did not find an upstream bug report for this
 error message.

 -----

 The errors in d7gonzo's qt5-qtbase-configure.zip are different:

 {{{
 Failed to resolve SDK path for 'macosx15.1'
 }}}
 {{{
 make: c: No such file or directory
 }}}
 {{{
 /bin/sh: o: command not found
 }}}

 I believe that's unrelated to the first problem and covered in #67589
 already.

 -----

 jamodeo12, if your problem was solved by following the steps at
 SequoiaProblems#CompilingCfails then that is yet a third problem unrelated
 to the first two.

 -----

 Please keep discussion of unrelated problems in their respective tickets.
 Grouping unrelated problems into one ticket makes it difficult to help
 everyone clearly. If you're not sure if your problem is the same, file a
 new ticket and someone will mark it as a duplicate of another ticket if
 that's what it turns out to be.

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