On 2024-07-06 12:09, Graham Inggs wrote: > Source: mayavi2 > Version: 4.8.1-5 > Severity: serious > Tags: ftbfs > X-Debbugs-Cc: [email protected], [email protected] > > Hi Maintainer > > mayavi2 FTBFS on ppc64el [1] and riscv64 [2], where it built > previously. I've copied what I hope > is the relevant part of the log below.
From a quick look, the problems appears when testing for the support of -march=native. ppc64el and riscv64 have in common that they don't support this GCC option. Normally this fails the following way: | $ gcc -march=native | gcc: error: '-march=native': ISA string must begin with rv32 or rv64 | gcc: fatal error: no input files | compilation terminated. However something sets LC_CTYPE to C.UTF-8, and pybuild also sets LC_ALL to C.UTF-8. This causes GCC to output a slightly different error message: | $ LC_CTYPE=C.UTF-8 gcc -march=native | gcc: error: ‘-march=native’: ISA string must begin with rv32 or rv64 | gcc: fatal error: no input files | compilation terminated. Note how the quotes are different and use non-ASCII characters. This is what chokes numpy distutils code. Now I am not sure why the problem suddenly happens. It might be related or not to a Python 3.12 change. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://aurel32.net
