I got mugged by a system’s (i.e. Debian testing) upgrade of libflint, going 
from 2.5.2 to 2.5.3. In Debian, libflint was libflint-2.5.2, with no 
“version independent” symlink libflint (nor even libflint-2.5). sage was 
linked “hard” against libflint-2.5.2.

Therefore, Sage crashed at start for lack of ibflint-2.5.2. Attempting to 
run configure again apparently succeeded but make failed to find the new 
library.

Workaround (compilation in progress) ./configure --with-system-flint=no ; 
make, which seems to involve a lot of other recompilations (including 
singular and arb…).

What is the recommended way to cope with such surprises ?


​

-- 
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/ccce2412-46a9-4e63-87b2-6d49252cdd1fo%40googlegroups.com.

Reply via email to