Did something change in Atlas ? On my fast machine (Core i7, 16 Gb RAM),
going fro 6.4beta4 to 6.4beta6, I'm still on Atlas compilation about 10
hours after 'export MAKE=make -j8 ; time make... This never happened on
this machine.
--
Emmanuel Charpentier
Le mardi 14 octobre 2014 22:09:23
Had to compile Atlas for three times in a row as well (beta4,5,6).
Something wrong with upgrading?
On Wed, Oct 15, 2014 at 8:47 AM, Emmanuel Charpentier
emanuel.charpent...@gmail.com wrote:
Did something change in Atlas ? On my fast machine (Core i7, 16 Gb RAM),
going fro 6.4beta4 to
[ Later ... ]
Make needed 658 minutes to complete. make ptestlong underway.
Weird...
Le mercredi 15 octobre 2014 08:47:18 UTC+2, Emmanuel Charpentier a écrit :
Did something change in Atlas ? On my fast machine (Core i7, 16 Gb RAM),
going fro 6.4beta4 to 6.4beta6, I'm still on Atlas
[ Still later ... ]
make ptestlong : all test passed in 1505 seconds.
__
Emmanuel Charpentier
Le mercredi 15 octobre 2014 09:27:35 UTC+2, Emmanuel Charpentier a écrit :
[ Later ... ]
Make needed 658 minutes to complete. make ptestlong underway.
Weird...
Le mercredi 15 octobre 2014
On Oct 14, 2014, at 13:09 , Volker Braun wrote:
Quick update mainly to fix the Python compilation issue.
Git develop branch or
http://sage.sagedev.org/home/release/sage-6.4.beta6.tar.gz
Built from scratch from the tarball. Results similar to those for 6.5.beta5:
Built w/o problems and
