Hi John, On 2015-09-10, John Cremona <john.crem...@gmail.com> wrote: > Has anyone started? AFter reading the above I just downloaded MeatAxe > 2.4.24 (2011) and very easily built it (make check OK); all one has to do > is copy Makefile to Makefile.conf and edit 2 lines, as I am sure you know.
... and then edit literally 1000s of lines in David Green's code and in my code. And rewrite the patches that are to be applied to MeatAxe. The problem doesn't lie in building MeatAxe. MeatAxe is a collection of executables, but what we need in the applications is a library of C-functions that my Cython code uses. So, part of the patches turns MeatAxe into a library. And the patches also add Strassen multiplication. But the interface of MeatAxe has thoroughly changed: Really, I don't think that there is any function or any type whose name has not changed. That's why it would involve a lot of work to use the most recent MeatAxe. > One way to proceed would be to make a new-style package out of the MeatAxe > source first. The your 2nd and 3rd parts would be separate, but with > MeatAxe as a dendency. The first part would take about 20 minutes to do.... No, since the patches need to be rewritten. And the 2nd and 3rd parts would also take rather long. That's why I suggest the following approach: 1. Turn the spkg into a new-style package with *least* effort. I.e., put the existing sources into some repository. In that way, the spkg can be used *NOW*. 2. Create a separate libmeataxe spkg (new-style of course), with patches rebased on the most recent upstream sources, and also providing the Cython wrapper that is currently burried in the cohomology spkg. 3. Adapt David Green's C programs and my Cython programs to the new version of MeatAxe. In the best case, it merely amounts in hundreds of search-and-replace actions. If I recall correctly, a couple of years ago I did some steps towards 2., so, in the best case, I can come up with libmeataxe-1.0 in a week or so. Best regards, Simon -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
