Observed on two systems running Debian testing (updated daily).
On these two systems, 9.6.rc4 (resp 9.6.rc4) gave satisfying results (already reported). After daily system update, the compilation of 9.6 went well, bit ptestlong gave catastrophic results : 57 (fifty seven, count 'em !) segfaults...
Enclosed an archive containing :
I'm at loss
-- Emmanuel Charpentier
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/b6cb0005953d0196ed460cd7159e9165b0eb18b4.camel%40free.fr.
Le lundi 16 mai 2022 à 13:17:53 UTC+2, Dima Pasechnik a écrit :
Have you rebuilt from scratch after the system update?
Nope. That’s usually unnecesary.
Any update of a dynamic library used by Sage can lead to lots of errors, unless the relevant components are rebuilt.
I’ll try that (i. e make distclean && ./configure --enable-download-from-upstream-url && make ptestlong) . Not especially fun…
After make dist-upgrade, rebuilding Sage faiis opn the documentation :
[sagemath_doc_html-none] NameError: Singular library 'freegb.lib' not found
[sagemath_doc_html-none]
[sagemath_doc_html-none] Note: incremental documentation builds sometimes cause spurious
[sagemath_doc_html-none] error messages. To be certain that these are real errors, run
[sagemath_doc_html-none] "make doc-clean doc-uninstall" first and try again.
This happens even after make doc-clean doc-uninstall. Still stuck.
Do you need logs/install.log ?
After perusing the failures log and some wild guesses, problem worked around by ./configure --with-system-python=no.
Does this problem deserve reporting to Debian (i. e. filing a ticket against Debianpython3 package) ?
Does this problem deserve reporting to Debian (i. e. filing a ticket against Debian
python3package) ?
After perusing the failures log and some wild guesses, problem worked around by
./configure --with-system-python=no.Does this problem deserve reporting to Debian (i. e. filing a ticket against Debian
python3package) ?
I just tried on Debian unstable, with the same Python version as in Debian testing, and I didn't get any error at all (all tests passed) either with Sage's own Python (3.10.3), or with Debian' s version (3.10.4).
Maybe it is something fixed between testing and unstable, or there is another issue, but in any case I don't think this problem deserves reporting to Debian.
--
Maxime