On 26/11/2019 01.51, Andreas Beckmann wrote: > On 26/11/2019 00.00, Benjamin Lorenz wrote: >> tldr: please rebuild normaliz and then try polymake again. > > Thanks for the analysis. binNMU of normaliz requested: #945504
Thanks. >> This is very weird but after some digging through backtraces, headers >> and bugzilla I am quite sure that this is caused by: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92267 > >> that debian already backported the fix for the gcc bug to gcc 9.2.1-16 > > Since you looked into this: when was this gcc bug introduced in Debian? According to the gcc bugtracker this was introduced upstream with gcc 9 in the following commit: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=260380 Thus it affects all 9.1 and 9.2 versions until 9.2.1-16 (9.2.1-20 contains the upstream backport). See also #935902 and #943401. I don't know when the default compiler for building packages was switched to gcc 9. > We should probably make a note to rebuild everything that was built with > the buggy libstdc++ before the release of bullseye... It don't think the bug affects many packages but this would be the safest choice... Benjamin
signature.asc
Description: OpenPGP digital signature