Bug#1004184: Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
- To: YunQiang Su <yunqiang.su@cipunited.com>, 1001168@bugs.debian.org
- Cc: Sandro Tosi <morph@debian.org>
- Subject: Bug#1004184: Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
- From: Chris Hofstaedtler <zeha@debian.org>
- Date: Mon, 19 Dec 2022 04:30:08 +0100
- Message-id: <[🔎] 20221219033005.orodj2bvepxl6vvg@percival.namespace.at>
- Reply-to: Chris Hofstaedtler <zeha@debian.org>, 1004184@bugs.debian.org
- In-reply-to: <9a8ccde9-9413-07ab-c4d3-2ee6073bf458@cipunited.com>
- References: <1217168619.775476.1641245161980.JavaMail.zimbra@synchrotron-soleil.fr> <handler.1001168.B1001168.164124516721048.ackinfo@bugs.debian.org> <Yaz0krBSE+sTDjxm@ramacher.at> <763116103.778345.1641247018277.JavaMail.zimbra@synchrotron-soleil.fr> <dca84a6d-46f4-3ee8-ccb9-1c9a0afc20ce@cipunited.com> <CAB4XWXxu5e0xjQw2JPptMF8viAO3eL+UU9Dv2iPxgAcLmEuGNw@mail.gmail.com> <Yaz0krBSE+sTDjxm@ramacher.at> <9a8ccde9-9413-07ab-c4d3-2ee6073bf458@cipunited.com> <Yaz0krBSE+sTDjxm@ramacher.at>
* YunQiang Su <yunqiang.su@cipunited.com>:
> 在 2022/1/14 23:30, Sandro Tosi 写道:
> > On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su <yunqiang.su@cipunited.com> wrote:
> > >
> > > On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel
> > > <frederic-emmanuel.picca@synchrotron-soleil.fr> 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
Reply to: