By the way, if the problem can be reduced to building the documentation
(that is, if "make build" succeeds but "make" does not), another option
would be to try "make doc-html-no-plot", or essentially equivalently do
export SAGE_DOCBUILD_OPTS+=' --no-plot'
make
It is possible that the
Miguel Angel,
Let me try and summarize the discussion so far and some options.
The failure:
- error while running 'make' on a CentOS machine with 2 GB of RAM
- occurred while building Sage's documentation, which is heavy on RAM
- likely an out of memory error; not surprising with only 2 GB of
When I am able to I am probably going to backup important parts of my VPS
and use Ubuntu on it instead. That way I can use the prebuilt Sage binaries.
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
Yes, that is the software: binary-pkg. I used it to try to make binaries
on my machine with 8GB RAM and then move the binaries over to the VPS as it
keeps crashing during the compile. Unfortunately it crashed on the virtual
machine I put on my local machine also, albeit in a different place.
Do you mean https://github.com/sagemath/binary-pkg ?
it is only needed in order to be able to make a binary installer.
you do not need it to build Sage in place.
4Gb should do.
You can also only do
make build
to skip building docs (they are online anyway)
--
You received this message
I tried to build the binaries locally but I ran into another error. This
time I believe it was during the building of the documentation (is there a
way to avoid this using the binary package builder?). At that point I
decided it was in my best interest to shell out $7/month for CoCalc..
The
On Monday, September 4, 2017 at 9:16:49 AM UTC+2, Jeroen Demeyer wrote:
>
> There is the message "Killed" which can normally only happen if
> something external kills Sage.
I had exactly this "Killed" yesterday and could resolve it by deleting my
$HOME/.sage folder.
Regards,
--
You received
Are you sure? The command "make build" skips the building of the documentation.
So you should not be able to get this error which happens during the building
of documentation.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
Hi,
i am not sure it is completely related, but i also get a recurrent failure
while building the doc, at the same position (plot3d). I am trying to run
a 32bit patchbot within a VM (which might be the common point).
You can get the log at:
Thank you. I got the same error even with 'make build' with the j1 flag. I
will compile from a local virtual machine and try going the route you
suggest.
Miguel-Angel Manrique
On Monday, September 4, 2017 at 2:07:25 PM UTC-7, Samuel Lelievre wrote:
>
> If you have access to another machine
If you have access to another machine with more RAM
and the same OS, you could produce binaries on that
machine and then install on the machine with less RAM
from the binaries you created. To create binaries, use:
https://github.com/sagemath/binary-pkg
--
You received this message because
Unfortunately I cannot add more RAM to the server. One day I hope to have
the server be in-house and to swim in many GB of RAM.
>
I will try these suggestions. Thanks again.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
I am trying to keep costs down. I would like to have more RAM, but it is
not in the budget.
--
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
you can try
MAKE="make -j1" make
to build the docs.
This should make sure you do not build it in parallel.
--
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
Sun 2017-09-03 20:27:44 UTC-5, Miguel-Angel Manrique:
> 2048MB RAM total, 4 core 64bit processor; the server was running
> webwork in the background, but no students have access yet.
>
> Building in parallel: no idea but I presume so. I didn't specify the
> number of threads to use during
There is the message "Killed" which can normally only happen if
something external kills Sage. A common case is the Linux OOM
(out-of-memory) killer which kills processes when the system runs out of
memory. Second, the docbuilder is known to use huge amounts of memory.
--
You received this
It is most certainly a parallel build in my opinion. Which means
that the screenshot is not very useful because we don’t see the
actual error.
So apart from Jeroen’s questions, that are all very sensible,
can we have access to the log file proper?
François
> On 4/09/2017, at 09:02, Jeroen
Possibly, you are running out of memory.
Are you building in parallel?
How much memory (RAM + swap) do you have?
Was your system particularly loaded while you were building Sage?
Is the error reproducible, i.e. does it happen again if you retry the build?
--
You received this message because
Hello,
I am having some trouble compiling sage on my VPS. I am running CentOS 7
and am simply running 'make' from a non-root account.
Thanks for any help. I have attached an image to show what is going on.
Miguel-Angel Manrique
19 matches
Mail list logo
