2020-12-27 14:50:57 +0200 | received badge | ● Notable Question
(source)
|
2020-12-27 14:50:57 +0200 | received badge | ● Popular Question
(source)
|
2019-11-09 00:57:36 +0200 | received badge | ● Famous Question
(source)
|
2019-06-13 13:32:41 +0200 | received badge | ● Popular Question
(source)
|
2019-05-17 11:52:52 +0200 | received badge | ● Notable Question
(source)
|
2018-10-08 17:54:58 +0200 | received badge | ● Popular Question
(source)
|
2018-07-14 22:00:13 +0200 | commented question | Unable to build sage with Python 2 Yes I decided not to go my usual way of adding bin to PATH. The symbolic link is actually very convenient and I will use it a lot more from now on. And thanks for enlightening me on sage and the installation process. |
2018-07-14 11:09:48 +0200 | commented question | Sagemath build stuck on compilation screen It never recovered. Not sure what happened but at the 6 hour mark, I decided to stop it by force. |
2018-07-13 23:46:00 +0200 | commented question | Unable to build sage with Python 2 @John Palmieri I managed to get it working. I had to run make ptest and all tests passed successfully, something must have been wrong with make ptest long . Now I can start using sage for math. I want to add sage to my PATH so I can run it from anywhere. Initially I wanted to add $HOME/sage/inst/bin to my PATH but this directory contains executables and symbolic links for a lot of programs such as python 2 and python 3. Would doing this cause conflicts with my system installed python? If so then is adding the SAGE_ROOT directory i.e. $HOME/sage/src/sage a better option? |
2018-07-13 17:44:06 +0200 | asked a question | Sagemath build stuck on compilation screen I ran make -j5 ptestlong and the compilation has been stuck on this screen for over 1 hour: [dochtml] [thematic_] dumping object inventory... done
[dochtml] [thematic_] build succeeded.
[dochtml] [thematic_] The HTML pages are in ../inst/share/doc/sage/html/en/thematic_tutorials.
[dochtml] Build finished. The built documents can be found in /home/user/sagemath/inst/share/doc/sage/html/en/thematic_tutorials
[dochtml] Elapsed time: 1729.2 seconds.
[dochtml] Done building the documentation!
Everything on the screen is static except for the blinking cursor at the end after the last line. I know the process is still running because ps -ef | grep -i make shows that the process has been running for nearly 6 hours now. - Has the build frozen or is this what i should expect from running
make -j5 ptestlong ? |
2018-07-13 16:54:13 +0200 | commented question | Unable to build sage with Python 2 Yes that's how I should have done it. make -j5 ptestlong has been running for nearly 5 hours now. Its been stuck on the part below for almost an hour now: [dochtml] [thematic_] dumping object inventory... done
[dochtml] [thematic_] build succeeded.
[dochtml] [thematic_] The HTML pages are in ../inst/share/doc/sage/html/en/thematic_tutorials.
[dochtml] Build finished. The built documents can be found in /home/user/sagemath/inst/share/doc/sage/html/en/thematic_tutorials
[dochtml] Elapsed time: 1729.2 seconds.
[dochtml] Done building the documentation!
There is no prompt but the cursor is still blinking. My system still sounds like its on full throttle and ps -ef | grep -i make shows that this process is still running. Is this normal or is something wrong? |
2018-07-13 11:35:33 +0200 | commented question | Unable to build sage with Python 2 Well, make -j5 ptestlong didn't work, it caused an error unless I ran make distclean first and now make -j5 ptestlong is saying I don't have a maths library. Edit: Your method would have worked (The clue why it didn't work is below.) checking whether make -j5 ptestlong sets $(MAKE)... no
checking whether make -j5 ptestlong supports nested variables... no
I was setting the environment variable export MAKE="make -j5 ptestlong" thinking that by running make it would execute this command. I was wrong because the message above shows that it doesn't set make . This works only when the ptestlong command is excluded which raises the suspicion that MAKE takes only one command. The way to do it is to run the command make -j5 ptestlong directly in the command line. |
2018-07-13 10:53:11 +0200 | commented question | Unable to compile sage I don't have logs in that path |
2018-07-12 21:18:46 +0200 | commented question | Unable to compile sage |
2018-07-12 20:13:59 +0200 | commented question | Unable to build sage with Python 2 To add to my first bullet point, shouldn't you run make distclean before running make again or make -j5 ptestlong especially when a build fails? |
2018-07-12 20:13:47 +0200 | received badge | ● Nice Question
(source)
|
2018-07-12 19:41:22 +0200 | commented question | Unable to build sage with Python 2 @John Palmieri gcc (GCC) 8.1.1 20180502 (Red Hat 8.1.1-1) .
I read on the github page that python test suite is already disabled, quote: "Python's test suite has
been disabled by default, because it causes failures on most
systems. To renable the Python testsuite, set the environment
variable SAGE_CHECK_PACKAGES to "python" - What do I have to do before running
make again? - And should i run
make ptestlong before running make -j5 or after it? - PPL is for numerical optimisation, is it not a bad idea to skip tests for it?
- What's the difference between
make ptest and make ptestlong ? Doesn't the latter test external dependencies like maple etc |
2018-07-12 19:34:59 +0200 | edited question | Unable to build sage with Python 2 I set export SAGE_CHECK="yes" to run tests on the spkgs before running make -j5 . This gives me another build breaking error, despite using python 2 to build sage Sage version: 8.3rc0
OS fedora 28 linux_86_x64 Last section from ppl-1.2.p1.log or see pastebin: In file included from ../../src/Pointset_Powerset_defs.hh:1454,
from ../../src/algorithms.hh:28,
from ../../src/ppl_include_files.hh:18,
from ../../src/ppl_header.hh:38,
from ../../tests/ppl_test.hh:27,
from equals1.cc:25:
../../src/Pointset_Powerset_templates.hh: In instantiation of 'Parma_Polyhedra_Library::Pointset_Powerset<PSET>::Pointset_Powerset(const Parma_Polyhedra_Library::Pointset_Powerset<QH>&, Parma_Polyhedra_Library::Complexity_Class) [with QH = Parma_Polyhedra_Library::Box<Parma_Polyhedra_Library::Interval<__gmp_expr<__mpq_struct [1], __mpq_struct [1]>, Parma_Polyhedra_Library::Interval_Info_Bitset<unsigned int, Parma_Polyhedra_Library::Test::Rational_Real_Open_Interval_Info_Policy> > >; PSET = Parma_Polyhedra_Library::NNC_Polyhedron]':
../../src/Pointset_Powerset_inlines.hh:262:43: required from 'bool Parma_Polyhedra_Library::Pointset_Powerset<PSET>::geometrically_equals(const
Parma_Polyhedra_Library::Pointset_Powerset<PSET>&) const [with PSET =
Parma_Polyhedra_Library::Box<Parma_Polyhedra_Library::Interval<__gmp_expr<__mpq_struct [1], __mpq_struct [1]>, Parma_Polyhedra_Library::Interval_Info_Bitset<unsigned int, Parma_Polyhedra_Library::Test::Rational_Real_Open_Interval_Info_Policy> > >]'
equals1.cc:44:50: required from here
../../src/Pointset_Powerset_templates.hh:66:29: internal compiler error: in type_dependent_expression_p, at cp/pt.c:25100
y_end = y.end(); i != y_end; ++i) {
~~^~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/ccb8H3zx.out file, please attach this to your bugreport.
make[7]: *** [Makefile:1245: equals1.o] Error 1
************************************************************************
Error testing package ppl-1.2.p1
********
|
2018-07-12 19:34:17 +0200 | commented question | Unable to build sage with Python 2 Linux federa 28. The only environment variables I set are SAGE_CHECK and MAKE . I will have put the log file on pastebin. |