On May 5, 8:52 pm, "William Stein" <wst...@xxxxxxxxx> wrote:
> On 5/5/07, mabshoff <Michael.Absh...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> My test case is to build the SAGE linbox package, then run the SAGE
> test suite. I also have a lot of randomized testing of linear algebra
> via my modular symbols package.
That sounds easy enough.
I am currently looking into adding Accelerate Framework support for
Linbox on MacOSX while I compile 2.5.0alpha2 on cygwin.
>
> > If you have your own code you can send them to me and I
> > can take a look.
>
> I'll try the latest svn and take a look myself. It's very easy to build
> the new linbox package, and it has some great things I really want
> to include in SAGE, e.g., Clement's new super-fast charpoly routine.
> If anything doesn't work I'll email both you and Clement.
>
I would suggest reporting them in linbox-use. The more traffic there
is the more people will come. I am very glad that the Linbox team
switched from the yahoo group to a google group. I believe that even
now you cannot even find the yahoo linbox group with the build in
search function!
>
> How about a script
> spkg-debug
> which is run instead of spkg-install if present and if one builds
> SAGE using "make sagedebug".
>
> This could be very complicated to maintain in general. E.g., when new
> versions of packages come out, instead of just updating spkg-install (which
> can already be incredibly complicated -- the spkg-install for singular), one
> also would have to do the same with spkg-debug. It also means that I have
> to run "make sagedebug" and make sure everything works on a whole
> bunch of different architectures after every package update before any
> new release of SAGE. Adding spkg-debug's and properly maintaining
> them would significantly increase the workload for making new SAGE
> releases, so it won't happen unless someone volunteers to help with it.
>
> > Is there also a way to finish the compilation and installation of a
> > spkg that had a build failure? I am currently stuck on cygwin with
> > libsingular and I can build it manually and run spkg-install, but when
> > I restart the build process with "make" it starts rebuild singular
> > from scratch :(. If I get it installed manually I can move forward
> > while waiting on somebody else to fix the build.
>
> The simplest answer is that if the package is called, e.g., foo-2.4.5,
> then if you just do (from SAGE_ROOT)
>
> touch spkg/installed/foo-2.4.5
>
> SAGE will henceforth assume that package was successfully installed.
> So, after doing
> . local/bin/sage-env
> and getting your package installed, just do touch as above, and you're
> good to go.
Great, that works for me.
> > > Best would be for you to send me an spkg-check script for each.
>
> > Will do. I am still working on an updated gdmodule that no longer uses
> > different Setup.py[.cygwin]
>
> Thanks.
Cheers,
Michael
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://www.williamstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
sage-devel-unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
|
