On Friday, 27 July 2012 23:07:34 UTC+8, Dima Pasechnik wrote: > > > > On Friday, 27 July 2012 22:33:55 UTC+8, Jean-Pierre Flori wrote: >> >> >> >> On Friday, July 27, 2012 4:15:10 PM UTC+2, kcrisman wrote: >>> >>> Tada! >>>>> >>>> >>>> >>> Wow! And it computes? The 1+1 in Ipython would be an int, after all; >>> is 1/2 = 0 or 1/2? >>> >>> >> I was able to compute the cardinality on an elliptic curve over F_2003 >> and over F_p where p was next_prime(2^100) which should use PARI. >> I kind of afraid of what a make ptestlong could output. >> > > the crucial thing to see is whether we will see fork() failures. > If not, we are in business. If yes, one might need to rebase all AND the > dlls that were built with Sage, > and try again... >
I started doing the same on my system, and the 1st obstacle I ran at was a fork() failure during the building of Python spkg. Well, this is OK, still. Probably can be fought with using rebase/rebaseall. What definitely has to be fixed, though, is blatant copying of Cygwin system dlls into SAGE_LOCAL/bin and SAGE_LOCAL/lib. Having two copies of a same dll is a huge no-no. Also, it's totally unneeded. E.g. this is done by readline and sqllight spkgs. It's easy to fix this along the fix in the patch spkg, where we just do not build readline on cygwin. > > > > >> >> About the NTL stuff, it might be solved by using the stuff provided by >> NTL itself rather than what we do in the spkg. >> NTL uses libtool for shared library, and I get no problem in Cygwin with >> that (or just little problems). >> > -- -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
