Bug#1004184: Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
* YunQiang Su : > 在 2022/1/14 23:30, Sandro Tosi 写道: > > On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su > > wrote: > > > > > > On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel > > > wrote: > > > > Built with gcc-11 and -fno-lto it doesn not work. > > > > > > > > > > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > > > ../../../test.py > > > > Segmentation fault > > > > > > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > > > PYTHONPATH=. ../../../test.py > > > > Segmentation fault > > > > > > > > > > > > > > It seems due to gcc-11. > > > > > > I tried to build with gcc-10 on sid, it works again. > > > > yes, that's what PICCA found and reported at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 > > > > are you going to look into a fix for gcc-11? > > > > Sure, I will dig it, since it may effect lots of other packages. So, was this ever fixed in gcc-11, or maybe in gcc-12? Chris
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
On Fri, 14 Jan 2022 23:34:57 +0800 YunQiang Su wrote: > 在 2022/1/14 23:30, Sandro Tosi 写道: > > On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su > > wrote: > >> > >> On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel > >> wrote: > >> > Built with gcc-11 and -fno-lto it doesn not work. > >> > > >> > > >> (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > >> ../../../test.py > >> > Segmentation fault > >> > > >> (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > >> PYTHONPATH=. ../../../test.py > >> > Segmentation fault > >> > > >> > > >> > >> It seems due to gcc-11. > >> > >> I tried to build with gcc-10 on sid, it works again. > > > > yes, that's what PICCA found and reported at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 > > > > are you going to look into a fix for gcc-11? > > > > Sure, I will dig it, since it may effect lots of other packages. > It is strange that -O1/-O2 fail, while -O0/-O3 succeed... > > Thanks, > > >
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
在 2022/1/14 23:30, Sandro Tosi 写道: On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su wrote: On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel wrote: > Built with gcc-11 and -fno-lto it doesn not work. > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ../../../test.py > Segmentation fault > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ PYTHONPATH=. ../../../test.py > Segmentation fault > > It seems due to gcc-11. I tried to build with gcc-10 on sid, it works again. yes, that's what PICCA found and reported at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 are you going to look into a fix for gcc-11? Sure, I will dig it, since it may effect lots of other packages. Thanks,
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su wrote: > > On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel > wrote: > > Built with gcc-11 and -fno-lto it doesn not work. > > > > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > ../../../test.py > > Segmentation fault > > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > PYTHONPATH=. ../../../test.py > > Segmentation fault > > > > > > It seems due to gcc-11. > > I tried to build with gcc-10 on sid, it works again. yes, that's what PICCA found and reported at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 are you going to look into a fix for gcc-11? Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel wrote: > Built with gcc-11 and -fno-lto it doesn not work. > > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ../../../test.py > Segmentation fault > (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ PYTHONPATH=. ../../../test.py > Segmentation fault > > It seems due to gcc-11. I tried to build with gcc-10 on sid, it works again.
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
Built with gcc-11 and -fno-lto it doesn not work. (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ../../../test.py Segmentation fault (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ PYTHONPATH=. ../../../test.py Segmentation fault
Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py)
I tested matplotlib built with numpy 0.17 0.19 0.21. each time I got the segfault. another difference was the gcc compiler. So I switched to gcc-10 (sid_mips64el-dchroot)picca@eller:~/matplotlib$ CC=gcc-10 python3 setup.py build if failed with this error lto1: fatal error: bytecode stream in file ‘build/temp.linux-mips64-3.9/matplotlib.backends._backend_agg/extern/agg24-svn/src/agg_bezier_arc.o’ generated with LTO version 9.4 instead of the expected 11.2 So I unactivated lto with this CFLAGS="-fno-lto" CC=gcc-10 python3 setup.py build at the end it seems that is does not segfault :) (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ../../../test.py Segmentation fault (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ PYTHONPATH=. ../../../test.py (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ ls matplotlib mpl_toolkits pylab.py toto.png Cheers
Bug#1001168: Info received (Bug#1001168: Info received ())
If I run in the sid chroot, but with the binaryed built from bullseye, it works. (sid_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ rm toto.png (sid_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ python3 test.py (sid_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ ls matplotlib mpl_toolkits pylab.py test.py toto.png
Bug#1001168: Info received ()
Here no error during the build of numpy 1.19.5 = 10892 passed, 83 skipped, 108 deselected, 19 xfailed, 2 xpassed, 2 warnings in 1658.41s (0:27:38) = but 109 for numpy 1.21... = 14045 passed, 397 skipped, 1253 deselected, 20 xfailed, 2 xpassed, 2 warnings, 109 errors in 869.47s (0:14:29) =
Bug#1001168: Info received ()
I investigated a bit more, it seems that cover is wrong. In a bullseye chroot it works $ python3 ./test.py (bullseye_mips64el-dchroot)picca@eller:~/matplotlib-3.5.0/build/lib.linux-mips64-3.9$ ls matplotlib mpl_toolkits pylab.py test.py toto.png I found that the test failed between the 3.3.4-2 and 3.3.4-2+b1 rebuild This binNMU was about python3.10 support, but in the same time numpy has changed from python3-numpy (= 1:1.19.5-1), to python3-numpy (= 1:1.21.4-2), I think that there is a non negligeable possibility for this bug to be triggered by the new numpy.
Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py)
I can confirm that the bullseye matplotlib does not produce a segfault
