Re: [sage-release] Re: Sage 6.10.rc2 binaries test

The binaries are all built with SAGE_INSTALL_GCC=yes to be as self-contained as possible. AFAIK a default Ubuntu install doesn't include a fortran compiler, for example. The LD_LIBRARY_PATH problem is fixed in Trac #19641 On Tuesday, December 22, 2015 at 9:40:25 AM UTC+1, Eric Gourgoulhon

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

Hi, Le vendredi 18 décembre 2015 16:46:19 UTC+1, leif a écrit : > > > Not strange (although probably a flaw), but all binaries are built with > SAGE_INSTALL_GCC=yes AFAIK, so Sage is mainly built with GCC 4.9.2 which > ships with an older libstdc++. > > The issue will presumably vanish when we

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

Le mardi 22 décembre 2015 09:58:41 UTC+1, Volker Braun a écrit : > > The binaries are all built with SAGE_INSTALL_GCC=yes to be as > self-contained as possible. AFAIK a default Ubuntu install doesn't include > a fortran compiler, for example. > > The LD_LIBRARY_PATH problem is fixed in Trac

[sage-release] Re: Sage 6.10.rc2 binaries test

Hi, I've tested sage-6.10.rc2-Ubuntu_15.10-x86_64.tar on a Ubuntu 15.10 computer and got the following issue: ./sage -n jupyter results in the error message: Please wait while the Sage Notebook server starts... [I 11:01:15.391 NotebookApp] Using MathJax: nbextensions/mathjax/MathJax.js [W

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

Fun! Your distro is built with a gcc that is more recent than the one your sage binary has been built with - and the libstdc++ from your distro is masked by the one from sage. François > On 18/12/2015, at 23:10, Eric Gourgoulhon wrote: > > Hi, > > I've tested

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

Yes I wrote the same problem on 16.04. I run sage -n=ipython and then I opened firefox. I noticed for me it's even better I just created an icon with sage -n=ipython (as application) so I don't see any terminal running and I run firefox. I noticed that file can be relocated in any dir, which

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

yes... But not fun :) Le 18/12/2015 11:16, Francois Bissey a écrit : Fun! Your distro is built with a gcc that is more recent than the one your sage binary has been built with - and the libstdc++ from your distro is masked by the one from sage. François On 18/12/2015, at 23:10, Eric

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

I noticed too, that sagemanifolds compiled perfect on the rc2 version. I think I have gcc 5xx. Le 18/12/2015 11:16, Francois Bissey a écrit : Fun! Your distro is built with a gcc that is more recent than the one your sage binary has been built with - and the libstdc++ from your distro is

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

Le vendredi 18 décembre 2015 11:16:05 UTC+1, François a écrit : > > Fun! Your distro is built with a gcc that is more recent than the one your > sage > binary has been built with - and the libstdc++ from your distro is masked > by the one from > sage. > What is strange is that the sage

Re: [sage-release] Re: Sage 6.10.rc2 binaries test

Eric Gourgoulhon wrote: > Le vendredi 18 décembre 2015 11:16:05 UTC+1, François a écrit : > > Fun! Your distro is built with a gcc that is more recent than the > one your sage > binary has been built with - and the libstdc++ from your distro is > masked by the one from > sage.

[sage-release] Re: Sage 6.10.rc2 binaries test

I've tested sage-6.10.rc2-Ubuntu_14.04-x86_64.tar.bz2. Looks good to me (the Jupyter issues are fixed). Thanks. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-release] Re: Sage 6.10.rc2 binaries test

Sorry I just read your message... http... works Le 18/12/2015 00:55, Henri Girard a écrit : Hi, I have these annoying message with ./sage -n=ipython I does work well on ./sage -n Any help ? Regards Henri ./sage -n=ipython