Dima Pasechnik

The problem is, however, in sagetex LaTeX class, in the part that generates the *.sage file. For the example above one gets ```import sagetex _st_ = sagetex.SageTeXProcessor('hh', version='2019/11/14 v3.4', version_check=True)...

@dandrake - perhaps you could quickly see how to fix this?

For 1., could you suggest a concrete example? (feel free to put into a PR, but if this sounds too hard, just post it here). Thanks!

thanks for the report, and please feel free to provide a PR to fix this issue.

Without an example for using this macro it's hard to guess what is does. Please provide one before we can go forward with this.

we have 0.19.1 meanwhile, any news here? `run-elm` is very useful for teaching purposes.

probably mpir-gmp.pc would be more appropriate for the compat case.

> Never seen anything like this before. Reading the gcc bugzilla, the issue seems to be incorrect longjmp/setjmp in sage itself, needing more volatile? Or did I read it wrong?...

see also https://trofi.github.io/posts/312-the-sagemath-saga.html - it does say that Sage needs more `volatile`, but not that anything else is amiss.

> Yes, this is just normal GAP rules, you need lots more volatile. Might be tricky to do with pyx, not sure if it is making variables behind the scenes...