>
> Or run 'make distclean' before switching Python versions.
>
For me, "make distclean" did not work.
--
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
Hi Frédéric,
On 2018-10-29, Frédéric Chapoton wrote:
> (1) there is no longer any line about "notebook()" (because the legacy
> sagenb is deprecated now)
Why not mention the jupyter notebook instead?
> (2) the python version which is used is displayed (because we will try to
> switch to
+1 for the new banner!
Eric.
--
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
Dear all,
Ticket #26460 contains a proposal for a refreshed banner :
┌┐
│ SageMath version 8.5, Release Date: 2018-12-25 │
│ Using Python 2.7. Type "help()" for help. │
I saw your message too late and recompiled everything, but now it works!
Thank you very much!
Le lundi 29 octobre 2018 10:06:56 UTC+1, Dima Pasechnik a écrit :
>
> maybe running ./configure followed by make will fix this.
> (as ./configure hopefully will tell Sage where to look for the "right"
The compilation is successful now !
It was enough to set SAGE_INSTALL_GCC='yes'.
Le lundi 29 octobre 2018 18:08:41 UTC+1, Paul Mercat a écrit :
>
>
> I tried to recompile with SAGE_INSTALL_GCC='yes', and now openblas compile
> (but the compilation of sage is not terminated).
>
> Le lundi 29
I tried to recompile with SAGE_INSTALL_GCC='yes', and now openblas compile
(but the compilation of sage is not terminated).
Le lundi 29 octobre 2018 17:04:30 UTC+1, Dima Pasechnik a écrit :
>
> So this must mean that you actually failed to gfortran package, no?
> (cause if you don't have
On Sunday, October 28, 2018 at 10:15:21 PM UTC-7, Kwankyu Lee wrote:
>
> How did your tentative fail ?
>>
>
> It was incremental build from sage with python2.
>
> So I tried to build in a freshly-cloned repository, and sage with python3
> was built successfully on my mac.
>
> Thanks!
>
This
So this must mean that you actually failed to gfortran package, no?
(cause if you don't have gfortran installed it would be built --- of
course it's madness to do on Linux, where
you can just install gfortran).
On Mon, Oct 29, 2018 at 4:49 PM 'Paul Mercat' via sage-devel
wrote:
>
> No, gfortran
No, gfortran was not installed, nor anaconda. I tried to compile sage on a
fresh new installation of Ubuntu.
Le lundi 29 octobre 2018 16:18:41 UTC+1, Dima Pasechnik a écrit :
>
> This looks like you have several versions of gfortran guts lying
> around. A leftover from (ana)conda?
>
> On Mon,
This looks like you have several versions of gfortran guts lying
around. A leftover from (ana)conda?
On Mon, Oct 29, 2018 at 3:02 PM 'Paul Mercat' via sage-devel
wrote:
>
> Hi !
>
> I tried to compile sage-8.4, and I have the following error.
>
> [openblas-0.2.20.p2] gfortran: error:
maybe running ./configure followed by make will fix this.
(as ./configure hopefully will tell Sage where to look for the "right" curl)
On Mon, Oct 29, 2018 at 8:52 AM 'Paul Mercat' via sage-devel
wrote:
>
> I tried that, but I get the same error.
> Do I need to recompile everything from the
I tried that, but I get the same error.
Do I need to recompile everything from the beginning ?
Le dimanche 28 octobre 2018 22:28:28 UTC+1, Samuel Lelievre a écrit :
>
> So the solution is to change your PATH before you start building Sage,
> so that the PATH does not contain Anaconda.
>
--
You
13 matches
Mail list logo
