Re: [sage-devel] Re: SageMath for Windows installer
Le jeudi 7 avril 2016 21:14:24 UTC+2, Emil Widmann a écrit : > > < I don't really wee why it could not be user-friendly, can you elaborate > on this? > > I think cygwin is a lot slower than virtualisation - or has this changed? > I did once a pretty big Sage computation on the same computer (involving big matrices and cython routines), both on Ubuntu and on Cygwin. Timings were essentially the same. I can't give you recent figures as my Ubuntu is broken since its last big update... Of course, if a package is specially optimized for Linux, then it will be much faster there, but otherwise there should not be a big difference (what is much slower on Cygwin, however, is Sagemath compilation, but this is not really relevant for users). Sébastien -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: SageMath for Windows installer
Le lundi 4 avril 2016 11:48:34 UTC+2, Erik Bray a écrit : > > > Yes, I think this approach is mainly useful for newcomers. The > majority of the problems you mentioned came in due to already having > various bits of this installed. I'm not quite sure I understand the point about latex. > I mean that sagemath in a VM will not interact well with other normal programs on my computer. Say I have mathematica or maple, will sagemath in VM be able to call them? > I'm -1 on Cygwin for a few reasons, but am working on building Sage > natively for Windows without a posix-compatibility layer. (Though I'm > not opposed to supporting Cygwin too of course but I don't think it's > the most user-friendly approach in the long term). > I don't really wee why it could not be user-friendly, can you elaborate on this? Note that there are cygwin programs that come with an all-in-one installer just as what you did for sagemath in VM, installing the bits of cygwin they need -- the user just has to click on OK once or twice, and then everything is working in a completely transparent way. Check out for instance Isabelle/HOL at https://isabelle.in.tum.de/ Of course, a native windows build would be even better, but that seems to be an order of magnitude more difficult since many programs in sage-the-distribution use the posix layer (PARI, for instance) > For an "average" user I think this installer is much friendlier than > any other currently working approach. > I agree completely. Sebastien -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: SageMath for Windows installer
Just tried it (on Windows 10 Pro 64 bits). In the end, it works, but I had to work a little bit for this: - when installing docker, it removed my git and installed its own git instead, without asking for anything. A little bit rude, as I liked my version better... - more serious, the sagemath VM did not start. The reason is that I had VirtualBox 4.2 already installed, while Docker requires VirtualBox 5.0 at least. Docker should have warned me about this, uninstalled the old VirtualBox and installed the new one instead, but it didn't. And then, of course, it could not start, without any error message. I had to dig a little bit to understand what was going on. It would be nice if the error messages of Docker were shown to the user. when the VM can not be installed. The second problem is likely to happen to anyone who has already used a Sagemath VM on Windows. For newcomers, there should be no issue, and then the installation is much smoother than with the previous system (just one file to download, click OK several times, and then everything is functional, so definitely a huge progress!). However, there are still the limitations of virtual machines (for instance, it can not use my systemwide latex, if I understand correctly). Cygwin looks to me to be a more promising route in this respect (sage on cygwin 64 is almost completely functional with good performance, with the exception of a buggy singular - hopefully, trac 17254 will bring improvements when/if completed). Sebastien -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Build error for sage 6.4 beta 5 under cygwin64
Le 09/01/2015 12:30, Jean-Pierre Flori a écrit : That is easy to fix. Just add gmp to the linked libraries in module_list.py for these files. Indeed, this is very easy, and works like a charm. After this, everything compiles, and a lot of things are working! (well, a lot of things are also broken, of course, including pari and ecm) -- 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.
[sage-devel] Build error for sage 6.4 beta 5 under cygwin64
The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that sage can now be built under cygwin64 almost out of the box. So, I tried, but I failed... Here are the problems I encountered, maybe someone with better computer skills can see what is going on. My sage version is sage 6.4beta5 with #17365 pulled. Very recent cygwin64 - First, pyzmq did not compile, because of undefined references in libzmq.a. It seems that the flag -no-undefined was not passed to ld while building libzmq.a (despite #17333). I hacked the makefile to make sure that the flag was passed when compiling zeromq, this solved the issue. - Then, while compiling sage proper, I get the following error gcc -I/usr/include/ncurses -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -I/home/Sebastien/sage/local/include -I/home/Sebastien/sage/local/include/csage -I/home/Sebastien/sage/src -I/home/Sebastien/sage/src/sage/ext -I/home/Sebastien/sage/local/include/python2.7 -c build/cythonized/sage/graphs/distances_all_pairs.c -o build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o -fno-strict-aliasing -w -fno-tree-dominator-opts gcc -shared -Wl,--enable-auto-image-base -L/home/Sebastien/sage/local/lib build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o -L/home/Sebastien/sage/local/lib -L/home/Sebastien/sage/local/lib/python2.7/config -L/home/Sebastien/sage/local/lib -lcsage -lpython2.7 -o build/lib.cygwin-1.7.33-x86_64-2.7/sage/graphs/distances_all_pairs.dll build/temp.cygwin-1.7.33-x86_64-2.7/build/cythonized/sage/graphs/distances_all_pairs.o: dans la fonction « __pyx_f_4sage_6graphs_19distances_all_pairs_bitset_clear »: /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010: référence indéfinie vers « __imp___gmpn_zero » /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:(.text+0x1493): relocalisation tronquée pour concorder avec la taille: R_X86_64_PC32 vers le symbole indéfini __imp___gmpn_zero /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010: référence indéfinie vers « __imp___gmpn_zero » /home/Sebastien/sage/src/build/cythonized/sage/graphs/distances_all_pairs.c:2010:(.text+0xba8e): relocalisation tronquée pour concorder avec la taille: R_X86_64_PC32 vers le symbole indéfini __imp___gmpn_zero collect2: erreur: ld a retourné 1 code d'état d'exécution Looks like a problem with mpir, or a linking problem... I can give more details or log files if needed. Sebastien -- 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.
[sage-devel] Re: Building Sage with Cygwin 32 bit
Le 08/04/2014 20:52, Evan Oman a écrit : I tried adding | ||defined(_CYGWIN_) There should be two underscores on each side of CYGWIN, i.e., __CYGWIN__ instead of _CYGWIN_ -- 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.
[sage-devel] Re: Building Sage with Cygwin 32 bit
I am also trying to compile sage (6.2 beta 4) under Cygwin. I got a working copy of sage, but the doc does not build (so, I can not try make test). Here is the beginning of the log: Building reference manual, first pass. [combinat ] Configuration error: [combinat ] There is a syntax error in your configuration file: invalid syntax (conf.py, line 1) [polynomia] Configuration error: [polynomia] There is a syntax error in your configuration file: invalid syntax (conf.py, line 1) [cmd ] Configuration error: [cmd ] There is a syntax error in your configuration file: invalid syntax (conf.py, line 1) And the list goes on like that for most directories, only [riemannia] succeeds. (the file combinat/conf.py is simply ../conf_sub.py). Any idea? For the record, here are the steps I followed to compile sage: - the patch trac.sagemath.org/ticket/15967 is necessary. - there are problems in rpy2. As mentioned in the previous message, one should add __CYGWIN__ in addition to Win32 and Win64 several times in rinterface/na_values.c. However, this is not enough: one still gets the following error gcc -shared -Wl,--enable-auto-image-base -L/home/Sebastien/sage-git/sage/local/lib build/temp.cygwin-1.7.28-i686-2.7/./rpy/rinterface/_rinterface.o -L/home/Sebastien/sage-git/sage/local/lib/python2.7/config -L/home/Sebastien/sage-git/sage/local/lib -L/home/Sebastien/sage-git/sage/local/lib/R//lib -L/home/Sebastien/sage-git/sage/local/lib/R/modules -lR -lpython2.7 -lR -o build/lib.cygwin-1.7.28-i686-2.7/rpy2/rinterface/_rinterface.dll build/temp.cygwin-1.7.28-i686-2.7/./rpy/rinterface/_rinterface.o: In function `EmbeddedR_init': /home/Sebastien/sage-git/sage/local/var/tmp/sage/build/rpy2-2.3.8/src/./rpy/rinterface/_rinterface.c:1333: undefined reference to `rl_completer_word_break_characters' /home/Sebastien/sage-git/sage/local/var/tmp/sage/build/rpy2-2.3.8/src/./rpy/rinterface/_rinterface.c:1334: undefined reference to `rl_completer_word_break_characters' /home/Sebastien/sage-git/sage/local/var/tmp/sage/build/rpy2-2.3.8/src/./rpy/rinterface/_rinterface.c:1336: undefined reference to `rl_basic_word_break_characters' /home/Sebastien/sage-git/sage/local/var/tmp/sage/build/rpy2-2.3.8/src/./rpy/rinterface/_rinterface.c:1337: undefined reference to `rl_basic_word_break_characters' collect2: error: ld returned 1 exit status error: command 'gcc' failed with exit status 1 (linking problem with readline, likely). I commented out the offending lines in _rinterface.c (I know this is not a proper fix, of course, but it is sufficient to get things to compile). - I had to rebase once. - Segmentation faults during zn_poly's tuning (in KS/FFT mul). Looks like http://trac.sagemath.org/ticket/13947. On the third attempt, everything went smoothly. Le 04/04/2014 22:03, Jean-Pierre Flori a écrit : IIRC, you should modify lines like the following one: https://bitbucket.org/lgautier/rpy2/src/a66387e12e2419141dadb7464ea9205595ef89af/rpy/rinterface/na_values.c?at=default#cl-206 to include __CYGWIN__ in addition to Win32 and Win64. -- 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.
[sage-devel] Re: Building Sage with Cygwin 32 bit
Le 06/04/2014 13:45, Sebastien Gouezel a écrit : I am also trying to compile sage (6.2 beta 4) under Cygwin. I got a working copy of sage, but the doc does not build (so, I can not try make test). Here is the beginning of the log: Building reference manual, first pass. [combinat ] Configuration error: [combinat ] There is a syntax error in your configuration file: invalid syntax (conf.py, line 1) (the file combinat/conf.py is simply ../conf_sub.py). The problem is that git on windows (msysgit) converts symlinks to text files containing the address of the symlinked file. So, it has nothing to do with sage, it is a problem with msysgit. Scripts to restore the symlinks are available at http://stackoverflow.com/questions/5917249/git-symlinks-in-windows -- 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.
[sage-devel] type of sin(0)
When trying to latex-print symbolic functions, I have seen the following
weird behavior:
sage: P=function('P',x)
sage: latex(P(x=sin(0)))
Traceback (click to the left of this block for traceback)
...
AttributeError: 'int' object has no attribute '_latex_'
The superficial reason for this behavior is that, if a symbolic function
has arguments without a _latex_ attribute, then its latex printing
fails. This is easy to fix, I have written a (very easy to review) patch
in TRAC 13632.
However, the deeper reason is that, even when 0 is a sage integer,
sin(0) is a Python integer:
sage: type(sin(0))
type 'int'
I was wondering if this behavior was by design, or how it could be fixed.
By the way, if I understand things correctly, it can even happen in a
similar situation that the product of two sage integers is a Python integer:
sage: var('x, y, z')
sage: P=function('P', x)
sage: latex(P(x=y*z)(y=0, z=0))
Traceback (click to the left of this block for traceback)
...
AttributeError: 'int' object has no attribute '_latex_'
SG
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
