On Wednesday, 7 October 2015 18:18:02 UTC+2, Jean-Pierre Flori wrote: > > As far as I remember, apart from the lack of POSIX compatibility on > Windows/MSYS, the main obstacle to "natively" compile Sage on Windows 64 > were: >
Just to clarify, I'm not talking about MSYS. That's a different thing entirely. MSYS2 has a posix layer. > * PARI which assumes that sizeof(long) == sizeof(void*), there is an > experimental branch fixing this: > http://pari.math.u-bordeaux.fr/archives/pari-dev-1505/msg00021.html > I am using Pari (not GP) today on Windows 64. It was minimal effort on my part to do so. I am not using a special branch. > * GAP memory allocation, no sure this is actually an issue, see > https://groups.google.com/d/msg/sage-devel/QXy_2KMbP1k/Z3cfpCieYzgJ for > "details". > Gasman might be an issue. My understanding is it tries to allocate all available memory up front. It's also not threadsafe. But this is already an issue for HPC Gap (so they use Boehm instead, as I understand it, albeit at a small performance cost). Bill. -- 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.
