Python3, yes. I put the output of gdb below
El jueves, 10 de mayo de 2018, 8:27:56 (UTC+2), Dima Pasechnik escribió:
>
> Well, fire up gdb, look at the place it crashes...
>
> It is python3, right? So it would help to see what F28 does with python3,
> and why it works outside of sage.
>
Well, fire up gdb, look at the place it crashes...
It is python3, right? So it would help to see what F28 does with python3, and
why it works outside of sage.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and
An update for the situation with respect to Fedora 28. In case my
installation, upgraded from previous versions, may have some problems I
retried in a virtual machine, using gcc-7.2 from sage, and I reached the
same place: a core dumped when trying to import crypt module in python3, no
issue
Thanks! Do you have any clue about why crypt module cannot be loaded?
El miércoles, 9 de mayo de 2018, 0:07:34 (UTC+2), Volker Braun escribió:
>
> Binaries are now on the way to the mirrors...
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-release"
Binaries are now on the way to the mirrors...
--
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+unsubscr...@googlegroups.com.
To post to this group,
I tried it.. I failed the first time because I did not used ./configure and
gcc package was not used. With ./configure, gcc was loaded, python2 is OK
but python3 still fails because of crypt module.
El lunes, 7 de mayo de 2018, 16:41:43 (UTC+2), John H Palmieri escribió:
>
> You could try
You could try setting the environment variable SAGE_INSTALL_GCC=yes to
force Sage to build its own version of gcc.
On Monday, May 7, 2018 at 6:56:53 AM UTC-7, Enrique Artal wrote:
>
> I have tried, but there are too many dependences. I will wait for
> binaries. I tried to compile on two
I have tried, but there are too many dependences. I will wait for binaries.
I tried to compile on two computers; In one of them python3 was compiled
but python2 failed on both. thanks for the tip, anyway.
El lunes, 7 de mayo de 2018, 10:37:56 (UTC+2), Dima Pasechnik escribió:
>
> You're using
You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known
to Python people this this does not work...
Can you install gcc-7 and make it the default compiler?
On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote:
>
> I was unable to compile it in Fedora 28. I attach
Thank you Volker for the release!
Built like a charm on Ubuntu 16.04 (from a fresh git clone) and make
ptestlong returned "All tests passed!".
Eric.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop
I use bionic AMD 64 and I compiled sage-8.2 git without any problem (but
openssl was lacking).
Le 06/05/2018 à 20:30, John H Palmieri a écrit :
Some version of gcc is in the prerequisites for linux, but if the
existing version is not good enough, Sage will build its own. On OS X,
Sage builds
Some version of gcc is in the prerequisites for linux, but if the existing
version is not good enough, Sage will build its own. On OS X, Sage builds
its own (for now). Also, the Sage gcc package is listed as standard, so it
should be included in the tarball. The point of the tarball being
FWIW, Starting from a 8.2rc2 tree, 8.2 + #24969 + #24585 builds and passes
ptestlong with no error whatsoever on Debian testing running on Core i7 +
16 GB RAM.
HTH,
--
Emmanuel Charpentier
Le dimanche 6 mai 2018 10:56:04 UTC+2, Volker Braun a écrit :
>
> The "master" git branch has been
Neither git nor curl are listed in README.md : are they downloaded an
compiled on a "virgin" system ? If so, no problem. If not, they should be
listed in the prerequisites...
--
Emmanuel Charpentier
Le dimanche 6 mai 2018 17:44:31 UTC+2, John H Palmieri a écrit :
>
> It doesn't contain git or
gcc is part of the prerequisites listed in README.md
--
Emmanuel Charpentier
Le dimanche 6 mai 2018 17:41:48 UTC+2, John H Palmieri a écrit :
>
> The "self-contained" source tarball is not self-contained: it (still) does
> not contains gcc. This has been true for at least the last several rc
>
The "self-contained" source tarball is not self-contained: it (still) does
not contains gcc. This has been true for at least the last several rc
releases, as I've reported here before.
On Sunday, May 6, 2018 at 1:56:04 AM UTC-7, Volker Braun wrote:
>
> The "master" git branch has been updated
The "master" git branch has been updated to Sage-8.2, of course
--
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+unsubscr...@googlegroups.com.
To
17 matches
Mail list logo
