On Mon, Oct 26, 2009 at 4:41 PM, John H Palmieri <jhpalmier...@gmail.com> wrote: > > > > On Oct 26, 3:54 pm, William Stein <wst...@gmail.com> wrote: >> On Mon, Oct 26, 2009 at 2:37 PM, John H Palmieri <jhpalmier...@gmail.com> >> wrote: >> >> >> >> > With Sage 4.2 on my machine running OS X 10.6, when I clone, I get >> > this: >> >> > Updating modification times for the documentation... >> > sage -docbuild --update-mtimes reference html >> > sphinx-build -b html -d /Applications/sage/devel/sage/doc/output/ >> > doctrees/en/reference /Applications/sage/devel/sage/doc/en/ >> > reference /Applications/sage/devel/sage/doc/output/html/en/reference >> >> > At this point, it hangs. Has anyone else seen this? >> >> I can replicate this. For me with 4.2 on OS X 10.6. On my Macbook >> Air laptop we have: >> >> d-69-91-158-18:~ wstein$ time sage -clone testclone >> Now cloning the current Sage library branch... >> hg clone sage sage-testclone >> updating working directory >> 1963 files updated, 0 files merged, 0 files removed, 0 files unresolved >> Copying over all Cython auto-generated .c, .cpp and .h files... >> Copying over build directory... >> Copying over all auto-generated reference manual .rst files... >> Copying over documentation output... >> Building sage-testclone... >> sage -b testclone >> >> ---------------------------------------------------------- >> sage: Building and installing modified Sage library files. >> >> Installing c_lib >> gcc -o src/convert.os -c -fPIC -I/Users/wstein/s/local/include >> -I/Users/wstein/s/local/include/python2.6 >> -I/Users/wstein/s/local/include/NTL -Iinclude src/convert.c >> ... >> >> Updating modification times for the documentation... >> sage -docbuild --update-mtimes reference html >> sphinx-build -b html -d >> /Users/wstein/s/devel/sage/doc/output/doctrees/en/reference >> /Users/wstein/s/devel/sage/doc/en/reference >> /Users/wstein/s/devel/sage/doc/output/html/en/reference >> ... >> >> Hangs with *0 activity* after a while. I never noticed this before, >> because I always hit control-c the second I see anything about Sphinx >> when cloning... >> >> Why do we do *anything* with Sphinx after cloning? Shouldn't we just >> copy everything over? > > Because if we just copy everything over, > Sphinx gets confused (for > reasons I don't understand) and thinks that everything needs to be > rebuilt.
Did you try copying with "cp -p"? William > So if you clone and change one file in the Sage library, > then if you ask to build the reference manual, it rebuilds the whole > thing from scratch. This new business with updating the modification > times was supposed to help with that, so that it would only build the > parts that had changed. > > John > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
