Hi John (2024.11.15_08:35:24_-0400)
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
...
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.
That is intentional. Python upstream does this to ensure that C
extensions are built with a compatible compiler.
Obviously, it didn't result in the right behaviour here. But I don't
think this is necessarily something we want to patch.
Stefano
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
