Source: python3-defaults
Version: 3.13.9-1
Severity: normal
X-Debbugs-Cc: debian-68k@lists.debian.org
User: debian-68k@lists.debian.org
Usertags: m68k

I do not think the 3.13.9 version bump is necessary, and going
back to 3.13.7 would allow m68k to participate in the 3.14 transition.

(Based on the timing I suspect the python3.13/14 FTBFS on m68k
started with GCC 15, but this is just a guess.)

--- PyGate Linux v1.5.1
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Tue, 2025-12-02 at 16:25 +0200, Adrian Bunk wrote:

Source: python3-defaults
Version: 3.13.9-1
Severity: normal
X-Debbugs-Cc: debian-68k@lists.debian.org
User: debian-68k@lists.debian.org
Usertags: m68k

I do not think the 3.13.9 version bump is necessary, and going
back to 3.13.7 would allow m68k to participate in the 3.14 transition.

(Based on the timing I suspect the python3.13/14 FTBFS on m68k
started with GCC 15, but this is just a guess.)

Yes, it did. There is a bug in Python upstream for which I provided a patch
but while the compilation error is fixed, the Python interpreter itself eve ntually
locks up for whatever I have not been able to figure out.

I think it would be best to build Python 3.14 with gcc-14 for the time bein
g
until the underlying problem has been sorted out. But I have just so much c apacity
I can spend on all of this before burning out.

Adrian

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- PyGate Linux v1.5.1
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi Adrian,

On Tue, 2025-12-02 at 15:31 +0100, John Paul Adrian Glaubitz wrote:

On Tue, 2025-12-02 at 16:25 +0200, Adrian Bunk wrote:

Source: python3-defaults
Version: 3.13.9-1
Severity: normal
X-Debbugs-Cc: debian-68k@lists.debian.org
User: debian-68k@lists.debian.org
Usertags: m68k

I do not think the 3.13.9 version bump is necessary, and going
back to 3.13.7 would allow m68k to participate in the 3.14 transition.

(Based on the timing I suspect the python3.13/14 FTBFS on m68k
started with GCC 15, but this is just a guess.)

Yes, it did. There is a bug in Python upstream for which I provided a pat

ch

but while the compilation error is fixed, the Python interpreter itself e

ventually

locks up for whatever I have not been able to figure out.

I think it would be best to build Python 3.14 with gcc-14 for the time be

ing

until the underlying problem has been sorted out. But I have just so much

capacity

I can spend on all of this before burning out.

FWIW, I have built and uploaded Python 3.14 manually now in a chroot where gcc-defaults
was downgraded to gcc-14 and that built without any problems. So it's defin itely related
to gcc-15.

Adrian

--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

--- PyGate Linux v1.5.1
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Wed, Dec 3, 2025 at 5:08?AM John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:

Hi Adrian,

On Tue, 2025-12-02 at 15:31 +0100, John Paul Adrian Glaubitz wrote:

On Tue, 2025-12-02 at 16:25 +0200, Adrian Bunk wrote:

Source: python3-defaults
Version: 3.13.9-1
Severity: normal
X-Debbugs-Cc: debian-68k@lists.debian.org
User: debian-68k@lists.debian.org
Usertags: m68k

I do not think the 3.13.9 version bump is necessary, and going
back to 3.13.7 would allow m68k to participate in the 3.14 transition

.

(Based on the timing I suspect the python3.13/14 FTBFS on m68k
started with GCC 15, but this is just a guess.)

Yes, it did. There is a bug in Python upstream for which I provided a p

atch

but while the compilation error is fixed, the Python interpreter itself

eventually

locks up for whatever I have not been able to figure out.

I think it would be best to build Python 3.14 with gcc-14 for the time

being

until the underlying problem has been sorted out. But I have just so mu

ch capacity

I can spend on all of this before burning out.

FWIW, I have built and uploaded Python 3.14 manually now in a chroot wher

e gcc-defaults

was downgraded to gcc-14 and that built without any problems. So it's def

initely related

to gcc-15.

From the GCC-15 release notes (<https://gcc.gnu.org/gcc-15/changes.html>):

C23 by default: GCC 15 changes the default language version for C
compilation from -std=gnu17 to -std=gnu23. If your code relies on o
lder
versions of the C standard, you will need to either add -std= to your
build flags, or port your code; see the porting notes.

The first thing I would try is to see if it is related to C23.

Jeff

--- PyGate Linux v1.5.1
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)