[MacPorts] #69320: On PPC Leopard, Mac OS X 10.5.8, py311-flit_core @3.9.0 does not build (which is required for py311-wheel)

[MacPorts]

#69320: On PPC Leopard, Mac OS X 10.5.8, py311-flit_core @3.9.0 does not build
(which is required for py311-wheel)
-----------------------------------+-------------------------
  Reporter:  ballapete             |      Owner:  (none)
      Type:  defect                |     Status:  new
  Priority:  Normal                |  Milestone:
 Component:  ports                 |    Version:  2.9.1
Resolution:                        |   Keywords:  leopard ppc
      Port:  py-flit py-flit_core  |
-----------------------------------+-------------------------

Comment (by ballapete):

 I assumed

 {{{
   py-bootstrap-modules @2022-12-23_0 (active) requested_variants=''
 platform='darwin 9' archs='noarch' date='2023-01-22T21:40:10+0100'
 }}}

 was too much out-of-date, so I rebuilt and reinstalled it. Afterwards I
 let `port show leaves` of Python 3.11 modules, and deleted them:

 {{{
 port uninstall py311-build py311-installer py311-setuptools py311-wheel
 }}}

 They were just `leaves`, nothing needed them. And they created some new
 `leaves`:

 {{{
 port uninstall py311-packaging py311-pyproject_hooks
 }}}

 So the base `Python 3.11` installation was quite clean and I

 {{{
 Successfully built installer-0.7.0-py3-none-any.whl
 Successfully built pyproject_hooks-1.0.0-py3-none-any.whl
 }}}

 and I invoked then

 {{{
 port -vsd build py311-build
 }}}

 which caused some disaster (just citing `port`'s comments and inserting
 some empty lines, not mentioning the need to install two or three other
 modules):

 {{{
 --->  Computing dependencies for py311-build

 --->  Staging py311-installer into destroot
 --->  Installing py311-installer @0.7.0_0
 --->  Activating py311-installer @0.7.0_0
 --->  Cleaning py311-installer
 --->  Removing work directory for py311-installer

 --->  Fetching distfiles for py311-packaging
 --->  Verifying checksums for py311-packaging
 --->  Checksumming packaging-23.2.tar.gz
 --->  Extracting py311-packaging
 --->  Extracting packaging-23.2.tar.gz
 --->  Configuring py311-packaging
 --->  Building py311-packaging
 Successfully built packaging-23.2-py3-none-any.whl
 --->  Staging py311-packaging into destroot
 --->  Installing py311-packaging @23.2_0
 --->  Activating py311-packaging @23.2_0
 --->  Cleaning py311-packaging
 --->  Removing work directory for py311-packaging

 --->  Staging py311-pyproject_hooks into destroot
 --->  Installing py311-pyproject_hooks @1.0.0_0
 --->  Activating py311-pyproject_hooks @1.0.0_0
 --->  Cleaning py311-pyproject_hooks
 --->  Removing work directory for py311-pyproject_hooks

 --->  Fetching distfiles for py311-build
 --->  build-1.0.3.tar.gz does not exist in
 /opt/local/var/macports/distfiles/py-build
 --->  Attempting to fetch build-1.0.3.tar.gz from
 http://distfiles.macports.org/py-build
 --->  Verifying checksums for py311-build
 --->  Checksumming build-1.0.3.tar.gz
 --->  Extracting py311-build
 --->  Extracting build-1.0.3.tar.gz
 --->  Configuring py311-build
 --->  Building py311-build
 }}}

 So I have now, when documenting:

 {{{
   python311 @3.11.8_0 (active) requested_variants='' platform='darwin 9'
 archs='ppc' date='2024-02-11T16:43:31+0100'
   py311-installer @0.7.0_0 (active) requested_variants='' platform='darwin
 any' archs='noarch' date='2024-02-11T22:12:24+0100'
   py311-packaging @23.2_0 (active) requested_variants='' platform='darwin
 any' archs='noarch' date='2024-02-11T22:14:33+0100'
   py311-pyproject_hooks @1.0.0_0 (active) requested_variants=''
 platform='darwin any' archs='noarch' date='2024-02-11T22:16:00+0100'
 }}}

 With this setup it does not work to install one kind of modules, others do
 build and install:

 {{{
   py311-setuptools @69.0.3_0 (active) requested_variants=''
 platform='darwin any' archs='noarch' date='2024-02-11T22:41:15+0100'
   py311-pip @24.0_0 (active) requested_variants='' platform='darwin any'
 archs='noarch' date='2024-02-11T22:51:42+0100'
 }}}

 With `pip3` I could try to install those modules that `port` cannot –
 because I seem to have now a faulty `build_wheel` routine?

 {{{
 DEBUG: system:  cd
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports
 .org_macports_release_tarballs_ports_python_py-
 build/py311-build/work/build-1.0.3" &&
 /opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11
 -m build --no-isolation --wheel --outdir
 /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports
 .org_macports_release_tarballs_ports_python_py-build/py311-build/work
 --skip-dependency-check
 * Building wheel...

 ERROR Backend subprocess exited when trying to invoke build_wheel
 Command failed:  cd
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports
 .org_macports_release_tarballs_ports_python_py-
 build/py311-build/work/build-1.0.3" &&
 /opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11
 -m build --no-isolation --wheel --outdir
 /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports
 .org_macports_release_tarballs_ports_python_py-build/py311-build/work
 --skip-dependency-check
 Exit code: 1
 Error: Failed to build py311-build: command execution failed
 }}}

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