Wookey <woo...@wookware.org> writes: >> 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?
I'm talking about remove polymake/arm64, not perl. d
