4el-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 wo
PICCA Frederic-Emmanuel
于2022年1月22日周六 17:28写道：
>
> Is it not better to use the
>
> DEB__MAINT_APPEND
>
> variable in order to deal with this issue ?
Thanks, you are right. the patch looks better now.
--
YunQiang Su
matplotlib-mips64el-o3.diff
Description: Binary data
Is it not better to use the
DEB__MAINT_APPEND
variable in order to deal with this issue ?
Graham Inggs 于2022年1月22日周六 16:48写道：
>
> On Sat, 22 Jan 2022 at 10:45, YunQiang Su wrote:
> > Sure. I will.
>
> Thank you!
Patch sent: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435
--
YunQiang Su
On Sat, 22 Jan 2022 at 10:45, YunQiang Su wrote:
> Sure. I will.
Thank you!
Graham Inggs 于2022年1月22日周六 16:42写道：
>
> On Sat, 22 Jan 2022 at 10:12, YunQiang Su wrote:
> > Let's have a try to build matplotlib with -O3, and try to build hkl with it.
> > If it works, we can workaround it for now.
> > I will continue to dig the real problem of gcc (maybe).
>
> To be clear, wil
On Sat, 22 Jan 2022 at 10:12, YunQiang Su wrote:
> Let's have a try to build matplotlib with -O3, and try to build hkl with it.
> If it works, we can workaround it for now.
> I will continue to dig the real problem of gcc (maybe).
To be clear, will you try building matplotlib with -O3 and if it
w
Graham Inggs 于2022年1月22日周六 15:42写道：
>
> Hi YunQiang Su
>
> Have you been able to make any progress with this issue?
>
> If not, then we should consider asking ftp-master for temporary
> removal of the affected mips64el packages from testing. We'd like to
> move the python3-defaults transition alo
Hi YunQiang Su
Have you been able to make any progress with this issue?
If not, then we should consider asking ftp-master for temporary
removal of the affected mips64el packages from testing. We'd like to
move the python3-defaults transition along.
Regards
Graham
s64el-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-
t'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,
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
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/bui
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
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
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)p
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) =
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
the full python backtrace
#8
#14 Frame 0x120debd80, for file
/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/lines.py,
line 2888, in draw (self=,
figure=<...>, _transform=None, _transformSet=False, _visible=True,
_animated=False, _alpha=None, clipbox=None, _clippath=None, _
Here the py-bt
(gdb) py-bt
Traceback (most recent call first):
File
"/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/lines.py",
line 2888, in draw
File
"/home/picca/matplotlib-3.5.0/build/lib.linux-mips64-3.9/matplotlib/artist.py",
line 50, in draw_wrapper
return
I can confirm that the bullseye matplotlib does not produce a segfault
This small script trigger the segfault.
#!/usr/bin/env python3
import matplotlib
import matplotlib.pyplot as plt
plt.figure()
plt.title("foo")
plt.savefig("toto.png")
bugs report are already filled on matplotlib
#1000774 and #1000435
I will try to see if this is identical...
Here the backtrace on mips64el
#0
agg::pixfmt_alpha_blend_rgba,
agg::order_rgba>, agg::row_accessor >::blend_solid_hspan(int,
int, unsigned int, agg::rgba8T const&, unsigned char const*)
(covers=0x100 , c=..., len=, y=166, x=,
this=)
at extern/agg24-svn/include/agg_color_rg
Source: hkl
Version: 5.0.0.2816-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
| ../../config/test-driver: line 112: 746832 Segmentation fault "$@" >>
"$log_file" 2>&1
| FAIL: trajectory.py
| ===
25 matches
Mail list logo
