On Feb 19, 5:29 am, Simon King <k...@mathematik.uni-jena.de> wrote:
> On Feb 19, 1:35 pm, mabshoff <mabsh...@googlemail.com> wrote:
>
> > Are you 100% certain you didn't build singular's NTL version at some
> > point? Maybe there is a second ntl.h?
>
> I checked. No ntl.h in the spkg.
Ok.
<SNIP>
> BTW, I think it would be a good thing to be able to up- or downgrade
> individual components of Sage. In this case, my motivation was a bug
> that only occured in Singular-3-0-4.
This will never work in any reliable way and I don't think we should
support this. The likeliest least amount of trouble for you to resolve
your problem is to ask Hans which fix resolved the problem you saw (in
case it is known) and you try to apply that fix to the 3-0-4.spkg.
> Aim: Change from singular-3-0-4-4-20080711.p1.spkg (included in
> sage-3.1.2) to singular-3-0-3-20070830.spkg (taken from the sage-2.8.4
> sources).
Again: This is *ancient* - if you drop it in an compiles - great, but
I don't see any reason at all to even attempt this since debuggability
goes to hell in an instant. There is one supported configuration of
Sage, i.e. the latest release, but you can experiment in any way you
need since this is open source. But to really drive this point home:
If you break Sage that way you get to keep the pieces :)
> 0. cd sage-3.1.2/
> 1. cp ../sage-2.8.4/spkg/standard/singular-3-0-3-20070830.spkg spkg/
> standard/
> 2. ./sage -i spkg/standard/singular-3-0-3-20070830.spkg
> 3. ./sage
> ->
> ...
> ImportError: /calcs2/king/Sagedevel/sage-3.1.2/local/lib/
> libsingular.so: undefined symbol: _ZTV10Evaluation
>
> As mentioned earlier in this thread, there are a couple of extensions
> that should be touched, followed by sage -b.
>
> 4. touch devel/sage-main/sage/libs/singular/singular.pyx
> touch devel/sage-main/sage/matrix/matrix_mpolynomial_dense.pyx
> touch devel/sage-main/sage/rings/polynomial/
> multi_polynomial_ideal_libsingular.pyx
> touch devel/sage-main/sage/rings/polynomial/
> multi_polynomial_libsingular.pyx
> 5. ./sage -b
>
> However, step 5. failed.
>
> I copied the info that ./sage -b gave me into some file
> installSAGE_B.log.
> You can find the two install.log
> athttp://sage.math.washington.edu/home/SimonKing/SPKG/
Ok.
> > A last resort is the charred earth policy of nuking that build and
> > starting over from scratch with a clean build where you do not even
> > build the 3-0-4 SIngular.spkg, but drop in the new one.
>
> Yes, as I said in one of my posts above, I did so successfully, except
> that I got the warning message about an undefined symbol and Singular
> being potentially slow.
Well, aside from the warning why do you care if a drop in replacement
+ build from scratch works? We will have to deal with that once we
upgrade to Singular 3-0-1 (or whatever will come once it is out), but
given that we will have access in an official way I don't worry about
that until it is available :)
> Cheers,
> Simon
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
