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) ? Le lundi 16 mai 2022 à 16:03:05 UTC+2, Emmanuel Charpentier a écrit : > On another machine, Sage builds, but `ptestlong` fails with a slightly > smaller list of failures : > > ``` > ---------------------------------------------------------------------- > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # 1 doctest > failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/dynamics/arithmetic_dynamics/projective_ds.py # Killed due to > abort > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/curves/projective_curve.py # Killed due to abort > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/curves/affine_curve.py # 48 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/rings/function_field/ideal.py # 12 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/curves/closed_point.py # 23 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/elliptic_curves/ell_field.py # Killed due to abort > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/rings/function_field/differential.py # 2 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/product_projective/rational_point.py # 1 doctest failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/curves/curve.py # 14 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/interfaces/singular.py # 5 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/curves/constructor.py # 4 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/schemes/curves/point.py # 6 doctests failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/libs/singular/function.pyx # 1 doctest failed > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/rings/polynomial/multi_polynomial_element.py # Killed due to abort > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/doc/en/constructions/algebraic_geometry.rst # Killed due to abort > sage -t --long --random-seed=292720829567961557971978070321731961282 > src/sage/libs/singular/singular.pyx # 1 doctest failed > ---------------------------------------------------------------------- > ``` > > Suggestions ? > > Le lundi 16 mai 2022 à 14:56:14 UTC+2, Emmanuel Charpentier a écrit : > >> 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 ? >> >> Le lundi 16 mai 2022 à 13:24:04 UTC+2, Emmanuel Charpentier a écrit : >> >>> 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… >>> >>> On Mon, 16 May 2022, 12:13 Emmanuel Charpentier, <[email protected]> >>>> wrote: >>>> >>>>> 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 : >>>>> >>>>> - config.log >>>>> - config.status >>>>> - logs\install.log >>>>> - logs/ptestlong.log >>>>> >>>>> 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 [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/sage-release/b6cb0005953d0196ed460cd7159e9165b0eb18b4.camel%40free.fr >>>>> >>>>> <https://groups.google.com/d/msgid/sage-release/b6cb0005953d0196ed460cd7159e9165b0eb18b4.camel%40free.fr?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/13df6201-9688-4613-a724-f93db9d031f0n%40googlegroups.com.
