Control: severity -1 important Hi Drew,
On Sat, 2025-09-27 at 15:23 +0200, Drew Parsons wrote: > mpi4py has started failing to build on sh4: > > building 'mpi4py.MPI' extension > creating build/temp.linux-sh4-cpython-313/src/mpi4py > /usr/bin/mpicc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -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 -DPYMPIABI=1 > -DHAVE_DLFCN_H=1 -DHAVE_DLOPEN=1 -Isrc -I/usr/include/python3.13 -c > src/mpi4py/MPI.c -o build/temp.linux-sh4-cpython-313/src/mpi4py/MPI.o > src/mpi4py/MPI.c: In function ‘__pyx_pymod_exec_MPI’: > src/mpi4py/MPI.c:289780:30: note: variable tracking size limit exceeded with > ‘-fvar-tracking-assignments’, retrying without > 289780 | static CYTHON_SMALL_CODE int __pyx_pymod_exec_MPI(PyObject > *__pyx_pyinit_module) > | ^~~~~~~~~~~~~~~~~~~~ > /tmp/cczUpbyN.s: Assembler messages: > /tmp/cczUpbyN.s:8852502: Error: value of 0001528e too large for field of 2 > bytes at 0003995f > error: command '/usr/bin/mpicc' failed with exit code 1 > > > Likely due to changes in gcc-15, aided and abetted by cython 3.0. > Upstream suggests building with -DCYTHON_LIMITED_API=1 > see https://github.com/mpi4py/mpi4py/pull/690#issuecomment-3337456651 Thanks a lot for investigating this issue and reporting it, I will have a look. However, since sh4 is not a release architecture, the severity should be lowered. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
