Fwd: Problems building farey_symbol.pyx on Cygwin

45 views
Skip to first unread message

kcrisman

unread,
Jul 27, 2012, 10:41:33 AM7/27/12
to sage-w...@googlegroups.com



On Friday, July 27, 2012 9:39:32 AM UTC-4, Jean-Pierre Flori wrote:

Tada!

On Friday, July 27, 2012 3:23:41 PM UTC+2, Jean-Pierre Flori wrote:


On Friday, July 27, 2012 3:19:38 PM UTC+2, Jean-Pierre Flori wrote:
As in #12104, libntl.dll could not be found.
Is it because it was moved rather than copied to libntl.dll.a in #9050?
And I can now start Sage!
I don't seem to suffer from #11551.

Emil Widmann

unread,
Jul 28, 2012, 6:32:28 AM7/28/12
to sage-w...@googlegroups.com
Congratulations!
If this Cygwin build is stable then there are now 3 different ways to run sage under the windows OS (Virtualisation, Colinux and Cygwin).

From my point of view Virtualisation is the superior variant for general use. I see the following main advantages:
Speed: Calculations in Virtualisation reach almost the same speed as if run under pure Linux. Colinux and Cygwin (an educated guess) need noticable overhead, estimated 20 - 30 %. Maybe there could be some benchmarking of the Cygwin version?
Stability: With the virtualisation it is possible to use a stable OS as a base vor the VM, this means building and upgrading sage is easier and faster in a well tested environment. In contrary maintaining a stable cygwin variant can prove difficult and time consuming (past experiences of others which were reported here)
Generality: The Virtual image can run on any platform (not just windows) if there is the Virtualisation software available. VirtualBox is available with an open licence. I suppose there should be a version available for most systems out there. The Virtual version is just a plain version of sage, no special adaptions to the code base are necessary.

I think there is a very good virtual windows version available - including documentation and support. I'd rather see efforts united in developing this approach further than to split strength between different versions. But of course the Cygwin version could have some special applications or advantages that I am not aware of.

Cheers, emil




 


I

Dima Pasechnik

unread,
Aug 6, 2012, 10:43:58 AM8/6/12
to sage-w...@googlegroups.com
On 2012-07-28, Emil Widmann <emil.w...@gmail.com> wrote:
> ------=_Part_291_20408341.1343471548910
> Content-Type: text/plain; charset=ISO-8859-1
>
>
>
> Am Freitag, 27. Juli 2012 15:41:33 UTC+1 schrieb kcrisman:
>>
>> See the thread
>> https://groups.google.com/forum/?fromgroups#!topic/sage-devel/Z95yxbAeaZ0on sage-devel!
>>>
> Congratulations!
> If this Cygwin build is stable then there are now 3 different ways to run
> sage under the windows OS (Virtualisation, Colinux and Cygwin).
>
Colinux? I doubt so. Colinux looks like a half-dead project,
unfortunately.


William Stein

unread,
Aug 6, 2012, 1:05:52 PM8/6/12
to sage-w...@googlegroups.com
Yes, but I think sage would easily run in colinux.  I've done so on several occasions with the main difficulty being disk space in their predefined 2gb virtual drive.

I wouldn't call colinux a viable approach though, since it crashes the host windows too much.

>
>
> --
> You received this message because you are subscribed to the Google Groups "sage-windows" group.
> To post to this group, send email to sage-w...@googlegroups.com.
> To unsubscribe from this group, send email to sage-windows...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

Reply all
Reply to author
Forward
0 new messages