Source: python3.13 Version: 3.13.0-2 Severity: normal User: debian-sup...@lists.debian.org Usertags: sh4 X-Debbugs-Cc: debian-sup...@lists.debian.org
Hello, due to bugs in the GCC SH backend [1], I had to build the python3.13 package on sh4 with a patched version of gcc-snapshot (version 1:20241004-1+sh4.2). Surprinsingly, this resulted in the build compiler "gcc-15" being stored into the Python configuration of the python3.13 so that some Python packages now FTBFS on sh4 with [3]: creating build/temp.linux-sh4-cpython-313 gcc-15 -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration \ -ffile-prefix-map=/<<PKGBUILDDIR>>=. -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat \ -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 \ -fPIC -I/usr/include/python3.13 -I/usr/include -c lxc.c -o build/temp.linux-sh4-cpython-313/lxc.o error: command 'gcc-15' failed: No such file or directory E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: /usr/bin/python3.13 setup.py build I: pybuild base:311: /usr/bin/python3 setup.py build Since I'm not sure whether this intentional or not (I would expect the Python configuration to store the name of the compiler with the help of the target triplet and not the versioned compiler binary), I'm reporting this issue here. At first sight, I have not seen where this information is actually stored in src:python3.13. Thanks, Adrian > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81426 > [2] > https://buildd.debian.org/status/fetch.php?pkg=python3.13&arch=sh4&ver=3.13.0-2&stamp=1731428213&raw=0 > [3] > https://buildd.debian.org/status/fetch.php?pkg=python3-lxc&arch=sh4&ver=1%3A5.0.0-2%2Bb2&stamp=1731521734&raw=0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
