On 2020-11-27 06:52 -0400, David Bremner wrote: > Wookey <woo...@wookware.org> writes: >> On 2020-11-17 21:19 +0000, Dominic Hargreaves wrote: >>> Thanks for your work on this. As of today polymake has been uploaded >>> to use gcc-9 which doesn't have this problem, so the perl transition >>> has been unblocked. >> >> I don't understand how this works, because Alex Coplan was able to reproduce >> the ICE all the way back to gcc6, and it's been in bugzilla since 2012. >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52830 >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91590 >> >> Still, immediate issue worked around and hopefully the compiler will >> get fixed one day. > > At the risk of being repetitive, this is only a workaround for the perl > transition, it does almost nothing for polymake on arm64. The package is > still RC buggy since it is compiled with a non-default version of > gcc. I'm still looking at an arch-specific removal for bullseye.
What are the implications of that? Wouldn't that make perl unbuildable on arm64 for the lifetime of the release which sounds like a big problem for everyone? i.e polymake is now pseudo build-essential. Obviously it's bad that polymake can only be built with an older compiler version, but we are at the mercy of compiler engineers fixing what appears to be a very old and difficult bug. Removing the package (and thus security support for perl) doesn't seem like something that serves our uses very well. Have I misunderstood the problem, or is this the situation? Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature
