You could build and run everything? Then you can take it. I've tried the perl-blead branch now, and it has required one small patch, as perl guts continue to change. This will arrive with the next regular polymake release, presumably somewhere in the falls.

Everything is using opt/homebrew/lib and opt/homebrew/include Shall I still remove them to "wno-unused" or something? No, homebrew directories should be fine. -Wno-unused is not about directories, it's rather to suppress warnings about some unused variables in legacy code. It's harmless t...

polymake uses homogeneous polynomials throughout.

Couldn't we detect such errors early enough, in toTropicalPolynomial() or in Hypersurface constructor, and produce a more comprehensible message?

Hi, Samurai ( https://github.com/michaelforney/samurai ) is a drop-in C99 replacement for the "ninja" command. If it's not too much trouble, could you allow ./configure to proceed if "samu" is installed instead of "ninja"? Or perhaps skip the check if $NINJA is set in ...

polymake 4.11 made it back to the Arch repos.

We are running the sanitizer in the configuration with libc++ from LLVM, where std::string has a small internal buffer for short strings (up to 6 bytes) overlapping with the pointer to heap-allocated long strings. This way, from the low-level perspective, the last character is always well-allocated ...

Well, it was primarily your insistence that forced me to have one more close look at that issue But the general warning remains: the current hack may cease to work with any new perl release.
BTW what happened to julia Debian package? Did they decide to move to snap, like firefox and chrome?

We tried to find such a hack but we failed. The problem is that the perl interpreter has hidden some vital functions which were necessary for parsing polymake perl code, starting with such elementary things as Matrix<Rational>. They can't be "revealed" from outside without modifying the pe...

... I haven't yet tracked down that issue. If anybody is interested in working with me on completing this patch, please get in touch I fully understand and appreciate your wish to help us in this misery, but I'm afraid any hacks we would try here will be in vain. Once the perl maintainers decided t...

The most probable reason is the incompatibility with the new perl version 5.38. This incompatibility turned out to be of such a fundamental nature that we decided to "divorce" polymake from perl altogether. This is, however, a large scale refactoring which takes substantial time. Until it'...