Re: [sage-devel] RAM to build Sage

On 2014-05-06 00:14, William Stein wrote: Hi, Does anybody know how much RAM is required to build Sage these days. With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB RAM results in failure (see below). Of course, I'm not using swap, and of course with swap you can do anything

[sage-devel] Re: html docbuilder hangs after first pass

That doesn't work. On Monday, May 5, 2014 10:39:19 PM UTC-7, Travis Scrimshaw wrote: > > 6.2.rc1 and 6.2.rc2 with Ubuntu 12.04 LTS. I'll try deleting the temp dir. > > Best, > Travis > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscr

[sage-devel] Re: html docbuilder hangs after first pass

6.2.rc1 and 6.2.rc2 with Ubuntu 12.04 LTS. I'll try deleting the temp dir. Best, Travis -- 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...@goo

Re: [sage-devel] Re: RAM to build Sage

On Monday, May 5, 2014 5:32:28 PM UTC-7, William wrote: > > On Mon, May 5, 2014 at 5:07 PM, John H Palmieri > > > wrote: > > > > > > On Monday, May 5, 2014 4:41:39 PM UTC-7, William wrote: > >> > >> On Mon, May 5, 2014 at 4:16 PM, John H Palmieri > >> wrote: > >> >> -leif > >> >> > >>

[sage-devel] Re: html docbuilder hangs after first pass

On Monday, May 5, 2014 6:18:56 PM UTC-7, Travis Scrimshaw wrote: > > Hey everyone, >As the title states. I've run "make doc-clean" along with all known > variants (including single and multi threaded) "make", "sage -docbuild all > html", "make doc" (I've also run "sage -sync-build" too). I

[sage-devel] html docbuilder hangs after first pass

Hey everyone, As the title states. I've run "make doc-clean" along with all known variants (including single and multi threaded) "make", "sage -docbuild all html", "make doc" (I've also run "sage -sync-build" too). I get some "gap: unable to extend workspace" while trying to build the doc. I

Re: [sage-devel] Re: RAM to build Sage

I have not successfully built the Sage docs on my .5/1 GB (I forget which) ram computer for quite some time. FWIW. -- 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 t

Re: [sage-devel] Re: RAM to build Sage

On Mon, May 5, 2014 at 5:07 PM, John H Palmieri wrote: > > > On Monday, May 5, 2014 4:41:39 PM UTC-7, William wrote: >> >> On Mon, May 5, 2014 at 4:16 PM, John H Palmieri >> wrote: >> >> -leif >> >> >> >> P.S.: If you haven't set MAKE, Sage "guesses" the number of threads to >> >> use to build t

Re: [sage-devel] Re: RAM to build Sage

On Monday, May 5, 2014 4:41:39 PM UTC-7, William wrote: > > On Mon, May 5, 2014 at 4:16 PM, John H Palmieri > > > wrote: > >> -leif > >> > >> P.S.: If you haven't set MAKE, Sage "guesses" the number of threads to > >> use to build the Sage library as well as the docs, AFAIK. > > > > > >

Re: [sage-devel] Re: RAM to build Sage

On Mon, May 5, 2014 at 4:16 PM, John H Palmieri wrote: >> -leif >> >> P.S.: If you haven't set MAKE, Sage "guesses" the number of threads to >> use to build the Sage library as well as the docs, AFAIK. > > > Right: Sage uses SAGE_NUM_THREADS to decide how many threads to use for > building spkgs

[sage-devel] Re: RAM to build Sage

On Monday, May 5, 2014 3:53:17 PM UTC-7, leif wrote: > > On Tuesday, May 6, 2014 12:14:50 AM UTC+2, William wrote: > >> Hi, >> >> Does anybody know how much RAM is required to build Sage these days. >> With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB >> RAM results in failu

[sage-devel] Re: RAM to build Sage

On Tuesday, May 6, 2014 12:14:50 AM UTC+2, William wrote: > Hi, > > Does anybody know how much RAM is required to build Sage these days. > With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB > RAM results in failure (see below). Of course, I'm not using swap, > and of course

[sage-devel] Re: RAM to build Sage

I regularly build Sage on an old machine with 2Gb RAM without problems (although I don't like running tests on it since it is single core). It has swap (I think 2.5Gb, can't check right now), but it does not seem to be used during compilation. However I saw that compiling/testing Sage requires

[sage-devel] RAM to build Sage

Hi, Does anybody know how much RAM is required to build Sage these days. With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB RAM results in failure (see below). Of course, I'm not using swap, and of course with swap you can do anything if you're willing to wait. That said, it wo

Re: [sage-devel] Re: bug "make doc-pdf" fatal error

2014-05-05 20:47 UTC+02:00, John H Palmieri : > > > On Monday, May 5, 2014 11:01:37 AM UTC-7, John H Palmieri wrote: >> >> I think this bug has been fixed: see >> http://trac.sagemath.org/ticket/16153. >> As Vincent says, though, there seem to be other problems with the PDF >> documentation. >> > >

[sage-devel] Re: interact.sagemath.org

Hi > I am one of the students who was selected for working with Sage for Google > Summer of Code. I will be working on the iOS app. One of the features I > want to implement is the ability to interact with > interact.sagemath.org > > Is there an

[sage-devel] interact.sagemath.org

Hi I am one of the students who was selected for working with Sage for Google Summer of Code. I will be working on the iOS app. One of the features I want to implement is the ability to interact with interact.sagemath.org Is there an API I can

[sage-devel] Re: sage-cleaner issues? clean up .sage/temp?

On Monday, May 5, 2014 11:46:52 AM UTC-7, John H Palmieri wrote: > > This surprised me a little bit: > > $ du -s -h ~/.sage/temp/jpalmieri/cleaner.log > 3.6G/Users/palmieri/.sage/temp/jpalmieri/cleaner.log > > Is there any reason to have such a large file lying around? Should it be > automa

[sage-devel] Fwd: SageDays62: Women In Sage (5)

-- Forwarded message -- From: Dr. Anna Haensch Date: Mon, May 5, 2014 at 12:12 PM Subject: Re: SageDays62: Women In Sage (5) To: "win...@lists.hawaii.edu" Here is an updated version: Hello All! We are very happy to announce SageDays62: Women In Sage (5) to take place July 28-A

Re: [sage-devel] sage-cleaner issues? clean up .sage/temp?

On Mon, May 5, 2014 at 11:46 AM, John H Palmieri wrote: > This surprised me a little bit: > > $ du -s -h ~/.sage/temp/jpalmieri/cleaner.log > 3.6G/Users/palmieri/.sage/temp/jpalmieri/cleaner.log > > Is there any reason to have such a large file lying around? Should it be > automatically cleane

[sage-devel] Re: bug "make doc-pdf" fatal error

On Monday, May 5, 2014 11:01:37 AM UTC-7, John H Palmieri wrote: > > I think this bug has been fixed: see http://trac.sagemath.org/ticket/16153. > As Vincent says, though, there seem to be other problems with the PDF > documentation. > Actually, I take that back. I just built the PDF docs for

[sage-devel] sage-cleaner issues? clean up .sage/temp?

This surprised me a little bit: $ du -s -h ~/.sage/temp/jpalmieri/cleaner.log 3.6G/Users/palmieri/.sage/temp/jpalmieri/cleaner.log Is there any reason to have such a large file lying around? Should it be automatically cleaned up every now and then? Also, I've noticed several times a "sage-

Re: [sage-devel] Re: Problem compiling sage 6.2.rc0-develop with macosx/mavericks

On Sunday, May 4, 2014 4:57:48 PM UTC-7, Andrew wrote: > > I now have a working version sage! I should qualify this: I have a working > version of 6.2.rc0 but I am still unable to compile 6.1.1. I think that > this is because of #15937 . This > patch is i

[sage-devel] Re: bug "make doc-pdf" fatal error

I think this bug has been fixed: see http://trac.sagemath.org/ticket/16153. As Vincent says, though, there seem to be other problems with the PDF documentation. John On Monday, May 5, 2014 5:55:16 AM UTC-7, Дима Щербаков wrote: > > System is Debian amd64 testing. > Hardware: Intel i7 4700MQ

Re: [sage-devel] bug "make doc-pdf" fatal error

Hi Dima, I got an error as well... but not the same (see the end of the log below). I guess that the focus is more on the html documentation and that the pdf is somehow broken with the different upgrade of the docbuild system. Vincent PS: the end of my log LaTeX Warning: Hyper reference `sage/c

[sage-devel] Re: Hoping to develop Game Theoretical capabilities in to Sage

On 5 May 2014 16:00, kcrisman wrote: > At this point you should start opening tickets! More technical discussion > can happen there, though of course discussion about optional/standard > packages needs to happen here. Thanks, I'll do this over the next week or so. I'll open three tickets (in l

[sage-devel] Re: Hoping to develop Game Theoretical capabilities in to Sage

> > > We've already corresponded about this privately, but I wanted to publicly >> support this proposal and offer help with it, given that it is a lot closer >> to my current research than anything else in Sage ;-) In particular, I >> think it is very important to think carefully about exactl

Re: [sage-devel] Re: Regarding Braid project and its integration in Sage

Wrapping a code that we cannot ship makes little sense. I say: if we are going to rewrite it, we better do it as part of the sage library from the beginning. If the license is not clarified soon, that is the path that i would follow. El lunes, 5 de mayo de 2014 14:49:42 UTC+2, Amit Jamadagni es

Re: [sage-devel] naive question on build process/patchbot

On Mon, May 5, 2014 at 7:10 AM, Ralf Stephan wrote: > Hello, > please bear with me and give me a hint why ... > > 1. isn't make just doing sage -b whenever nothing in >lib/ is changed (or any suitable definition of lib)? >A counterexample would suffice. > > 2. why does patchbot make and te

[sage-devel] naive question on build process/patchbot

Hello, please bear with me and give me a hint why ... 1. isn't make just doing sage -b whenever nothing in lib/ is changed (or any suitable definition of lib)? A counterexample would suffice. 2. why does patchbot make and test twice per ticket, even with skip-base? i.e., is it not worthw

[sage-devel] Fwd: SageDays62: Women In Sage (5)

-- Forwarded message -- From: Dr. Anna Haensch Date: Mon, May 5, 2014 at 12:27 AM Subject: SageDays62: Women In Sage (5) To: "win...@lists.hawaii.edu" Hello All! We are very happy to announce SageDays62: Women In Sage (5) to take place July 28-August 1, 2014 at the Lodge at Wel

Re: [sage-devel] Re: Regarding Braid project and its integration in Sage

But the worry is that the maintainer has not given his thoughts on the subject of license. I know re-writing is altogether at a different level (keeping in mind the extensive results that Braid program provides), but considering the advantages like total control (rather than wrapping, with compiler

Re: [sage-devel] Re: Regarding Braid project and its integration in Sage

Well, we still have the license issue. Without the explicit permission of the author we cannot distribute a derivative work under the GPL. El lunes, 5 de mayo de 2014 14:32:36 UTC+2, Amit Jamadagni escribió: > > Yes, with some pointers I guess I can pull it off. But re-writing would > make it se

[sage-devel] Re: setuptools install problem

This is not SMC specific. Also the CentOS machine running patchbot has these build failures occasionally. http://patchbot.sagemath.org/log/8734/CentOS/6.5/x86_64/2.6.32-431.5.1.el6.x86_64/kepler.math.osu.edu/2014-04-30%2014:37:38%20-0400 On Monday, May 5, 2014 8:56:17 AM UTC+2, Ralf Stephan wrote

Re: [sage-devel] Re: Regarding Braid project and its integration in Sage

Yes, with some pointers I guess I can pull it off. But re-writing would make it set once for all. That is what I think. On Mon, May 5, 2014 at 5:58 PM, mmarco wrote: > Amit, how do you feel about that patching? Do you feel capable of doing it? > > El sábado, 3 de mayo de 2014 22:29:23 UTC+2, Am

[sage-devel] Re: Regarding Braid project and its integration in Sage

Amit, how do you feel about that patching? Do you feel capable of doing it? El sábado, 3 de mayo de 2014 22:29:23 UTC+2, Amit Jamadagni escribió: > > Hello all, > We (me under the mentorship of Miguel) have been working on > the implementation of Knot theory in Sage as a part of GSoC