>From the log: [sagelib-9.7] sage/rings/polynomial/multi_polynomial_libsingular.cpp: In function ‘PyObject* __pyx_pf_4sage_5rings_10polynomial_28multi_polynomial_libsingular_23MPolynomial_libsingular_106lift(__pyx_obj_4sage_5rings_10polynomial_28multi_polynomial_libsingular_MPolynomial_libsingular*, PyObject*)’: [sagelib-9.7] sage/rings/polynomial/multi_polynomial_libsingular.cpp:35067:120: error: ‘pTakeOutComp1’ was not declared in this scope; did you mean ‘pTakeOutComp’?
Fixed in https://trac.sagemath.org/ticket/34851 Workaround: Use configure --without-system-singular On Friday, January 13, 2023 at 12:25:14 AM UTC-8 tdumont wrote: > Hi, > > I must first say that using Debian Testing as an operatin system for > compiling Sage is not a good idea : as every day, about 50 packages are > updated, it happens frequently that the a library used by Sage, or the > compilers are updated. Then your compiled Sage no more works, and you > need to compile it again...so, avoid Debian Testing ! > > But ok. I am on Debian Testing. Since my last system upgrade, I can no > more compile sage. > > My compilers: > gcc: gcc version 12.2.0 (Debian 12.2.0-13) > > As I cannot solve the problem my self, the install.log is associated to > this mail. > Yours, > Thierry. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/915a7425-37fe-4f3e-8660-b9006cfa40den%40googlegroups.com.
