Opened 3 months ago

Last modified 3 months ago

#69319 new defect

python311 @3.11.8 still cannot build modules on PPC Leopard, Mac OS X 10.5.8

Reported by: ballapete (Peter "Pete" Dyballa) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.9.1
Keywords: leopard ppc Cc: jmr@…
Port: python311

Description

The update does not cure the problem described in #69106. Interestingly the crashes started earlier than thought:

-rw------- 1 pete  9708  9. Feb 20:16 Library/Logs/CrashReporter/Python_2024-02-09-201603_Leopard.crash
-rw------- 1 pete  9714  9. Feb 23:46 Library/Logs/CrashReporter/Python_2024-02-09-234603_Leopard.crash
-rw------- 1 pete  9714  9. Feb 23:58 Library/Logs/CrashReporter/Python_2024-02-09-235834_Leopard.crash
-rw------- 1 pete  9714 10. Feb 00:29 Library/Logs/CrashReporter/Python_2024-02-10-002927_Leopard.crash
-rw------- 1 pete 11815 10. Feb 00:38 Library/Logs/CrashReporter/Python_2024-02-10-003829_Leopard.crash
-rw------- 1 pete  9653 10. Feb 00:42 Library/Logs/CrashReporter/Python_2024-02-10-004208_Leopard.crash
-rw------- 1 pete  9653 10. Feb 00:45 Library/Logs/CrashReporter/Python_2024-02-10-004500_Leopard.crash
-rw------- 1 pete  9714 10. Feb 17:00 Library/Logs/CrashReporter/Python_2024-02-10-170014_Leopard.crash
-rw------- 1 pete  9714 10. Feb 17:32 Library/Logs/CrashReporter/Python_2024-02-10-173157_Leopard.crash
-rw------- 1 pete 11815 10. Feb 17:37 Library/Logs/CrashReporter/Python_2024-02-10-173657_Leopard.crash
-rw------- 1 pete  9714 11. Feb 01:00 Library/Logs/CrashReporter/Python_2024-02-11-005957_Leopard.crash
-rw------- 1 pete  9714 11. Feb 01:07 Library/Logs/CrashReporter/Python_2024-02-11-010714_Leopard.crash
-rw------- 1 pete  9714 11. Feb 17:45 Library/Logs/CrashReporter/Python_2024-02-11-174526_Leopard.crash
  python311 @3.11.7_0 requested_variants='' platform='darwin 9' archs='ppc' date='2024-02-09T19:23:47+0100'
  python_select-311 @0.3_1 (active) requested_variants='' platform='any any' archs='noarch' date='2024-02-09T18:17:07+0100'
  python3_select-311 @0.1_1 (active) requested_variants='' platform='any any' archs='noarch' date='2024-02-09T18:17:50+0100'
  py311-packaging @23.2_0 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-09T19:40:45+0100'
  py311-pyproject_hooks @1.0.0_0 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-09T19:41:08+0100'
  py311-build @1.0.3_0 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-09T19:41:24+0100'
  py311-installer @0.7.0_0 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-09T19:41:44+0100'
  py311-setuptools @69.0.3_0 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-09T19:42:12+0100'
  xorg-xcb-proto @1.16.0_0+python311 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-09T23:26:11+0100'
  xorg-libxcb @1.16_0+python311 (active) requested_variants='' platform='darwin 9' archs='ppc' date='2024-02-09T23:44:19+0100'
  py311-libxml2 @2.11.5_0 (active) requested_variants='' platform='darwin 9' archs='ppc' date='2024-02-10T00:25:24+0100'
  itstool @2.0.7_2+python311 (active) requested_variants='+python311' platform='any any' archs='noarch' date='2024-02-10T00:25:39+0100'
  py311-pygments @2.17.2_0 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-10T11:55:48+0100'
  boost176 @1.76.0_10+no_single+no_static+python311 (active) requested_variants='+python311' platform='darwin 9' archs='ppc' date='2024-02-10T16:30:56+0100'
  py311-wheel @0.42.0_0 (active) requested_variants='' platform='darwin any' archs='noarch' date='2024-02-10T16:59:33+0100'
  python311 @3.11.8_0 (active) requested_variants='' platform='darwin 9' archs='ppc' date='2024-02-11T16:43:31+0100'

Possibly the crashes come from port trying to build py311-meson, which happened quite often I am attaching the last crash log and main.log.

Attachments (2)

main.log (100.3 KB) - added by ballapete (Peter "Pete" Dyballa) 3 months ago.
Main.log from PPC Leopard, Mac OS X 10.5.8, trying to build py311-meson
Python_2024-02-11-174526_Leopard.crash (9.5 KB) - added by ballapete (Peter "Pete" Dyballa) 3 months ago.
Corresponding system crash log from PPC Leopard, Mac OS X 10.5.8, trying to build py311-meson

Download all attachments as: .zip

Change History (6)

Changed 3 months ago by ballapete (Peter "Pete" Dyballa)

Attachment: main.log added

Main.log from PPC Leopard, Mac OS X 10.5.8, trying to build py311-meson

Changed 3 months ago by ballapete (Peter "Pete" Dyballa)

Corresponding system crash log from PPC Leopard, Mac OS X 10.5.8, trying to build py311-meson

comment:1 Changed 3 months ago by ballapete (Peter "Pete" Dyballa)

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

comment:2 Changed 3 months ago by jmroot (Joshua Root)

Source for _Py_dg_infinity is here if you want to investigate: https://github.com/python/cpython/blob/v3.11.8/Python/dtoa.c#L1430

Note that that function no longer exists in 3.12 and later, as C99's INFINITY is used instead.

comment:3 in reply to:  2 Changed 3 months ago by ballapete (Peter "Pete" Dyballa)

Replying to jmroot:

Source for _Py_dg_infinity is here if you want to investigate: https://github.com/python/cpython/blob/v3.11.8/Python/dtoa.c#L1430

No, I do not understand how to debug the issue, how to make Python show what it is doing.

Note that that function no longer exists in 3.12 and later, as C99's INFINITY is used instead.

You're trying to make me use the official version! This would be an option. I presume those few ports that depend on Python 3.10 or 2.7 will also work with Python 3.12 when they can accept Python 3.11. At least it would be a test…

comment:4 Changed 3 months ago by jmroot (Joshua Root)

I can't debug this either since I have no ppc hardware.

Note: See TracTickets for help on using tickets.