[MacPorts] #70585: py310-pyqt5-webengine upgrade broken on port version 2.10.1 on Ventura 13.6.7

[MacPorts]

#70585: py310-pyqt5-webengine upgrade broken on port version 2.10.1 on Ventura
13.6.7
------------------------------------+------------------------
  Reporter:  Alex11N                |      Owner:  reneeotten
      Type:  defect                 |     Status:  assigned
  Priority:  Normal                 |  Milestone:
 Component:  ports                  |    Version:  2.10.1
Resolution:                         |   Keywords:
      Port:  py310-pyqt5-webengine  |
------------------------------------+------------------------

Comment (by Alex11N):

 I've **always** used xcode-select to install the CLTs (and recently found
 that I can install the CLTs without Xcode installed).

 Right. I've:

 1.  deleted and 'clean-ish' re-installed Xcode and rebooted;

 2. deleted (completely hosed) and reinstalled the CLTs

 3. reinstalled macports 2.10.1 using the package downloaded from the
 website as opposed to 'selfudate', in an attempt to get bash to take up
 the PATH additions (it didn't, so i did it by hand in ~/.bash_rofile)

 4. ran sudo port -v migrate' on my installation - port then deleted
 everything that was @active and repopulated the installation with its
 snapshot-1. it's notable that very few ports out of the few hundred
 installed actually went through the build process - things like clang and
 llvm that used to take hours to compile were simply dropped into place
 pre-built. One exception to this was **PY310-PYQT5-WEBENGINE** (there were
 a few otherswhose names I couldn't/didn't catch) - and it failed to build
 at the same macos13.3.sdk choke-point.

 5. ran sudo port -v install py310-pyqt5-webengine after the migration had
 finished and it failed to build FAILED AGAIN, for exactly the same reason,
 i.e,, the macOS13.3.SDK - which is part of the latest CLT that I forced
 xcode-select to download and install.

 The initial failed build attempts that generated this trac ticket were
 using zsh as my terminal shell; the migration sequence and the last
 'webengine' build were running on /opt/local/bin/bash in terminal.

 It looks as though there is **nothing** that I can do to to fix the
 macos13.3.sdk problem as far as I know: the locations are as Apple has
 decreed, and almost everything else that I've built-installed on my
 macports setup have been fine. 'py310-pyqt5-webengine' is definite
 outlier.  I don't understand why the SDK subdir in the CLT directory has
 versions up to 13.3 but NOT 14.x - other than that Apple hasn't updated
 the CLTs in (quite) a while. The CLTs seem to add an extra level of
 complexity since the SYSTEM has waht appears to be the same build tools,
 etc, embedded witihn it.

 This is doing what's left of my meagre head in.

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