Dear developers,
Singular-3-0-4 introduced a bug that made one of my computations not
work. It did work with Singular-3-0-3, and some tests indicate that it
would also work with the current CVS version of Singular-3-1-0.
So, I tried two things
1. Take a Singular-3-0-3-spkg from a previous sage release, and
install it.
2. Create an spkg for Singular-3-1-0-beta, and install it.
When I did "sage -f singular...spkg" with either of the two spkgs,
there was no error message, and "sage -singular" worked. But when I
started sage, there was a segfault.
So, my first question: How can I change (downgrade) the Singular-spkg
without to destroy the rest of sage? Is there something else that
needs to be re-built after installing a different spkg?
Next, I took the sage-3.2.3 sources, replaced the singular-3-0-4 spkg
with my singular-3-1-0-beta spkg, and built sage from scratch. This
mainly worked, but when I start sage or "sage -singular", I get the
warning:
// ** Could not open dynamic library: /home/king/SAGE/devel/sage-3.2.3/
local/lib/p_Procs_FieldIndep.so
// ** Error message from system: /home/king/SAGE/devel/sage-3.2.3/
local/lib/p_Procs_FieldIndep.so: undefined symbol: __dso_handle
// ** Singular will work properly, but much slower.
// ** See the INSTALL section in the Singular manual for details.
In spite of the warning, everything works, and Singular is *not* slow.
So, my second bunch of questions is just out of curiosity:
Why is Singular unable to open the dynamic library? It would have the
permission.
According to nm p_Procs_FieldIndep.so, the symbol __dso_handle is
indeed undefined. Why? I.e., where should it usually come from?
Best regards
Simon
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
