Julien Puydt wrote:
Hi,
I'm making experiments building sage with a mix of spkg / system
packages ; things are starting to take shape, and I'm now able to finish
the 'build' step.
For the 'doc' step, I get a strange behaviour : the doc seems to build
correctly, but then at some point, it tells me the build was a success
in a directory... and it just sits there. Nothing happens anymore. No
error, no warning. I see the processes in top and they look happy. I'm
pretty sure 'fine' would be a better word, but 'happy' looks more
descriptive and funnier: they obviously enjoy running!
First of all:
* I'm pretty sure processes can be happy while asleep as well.
* What Sage version is this based on? (And which spkgs did you
"replace" by system ones? Versions?)
* What platform (OS, CPU)?
I first thought it could be some kind of threading issue where several
processes were waiting for access to some cache, but it also happens
with SAGE_NUM_THREADS set to 1.
AFAIK, docbuilding currently uses Python's multiprocessing even if
SAGE_NUM_THREADS=1; cf. Stephen Montgomery's (apparently similar)
problems on FreeBSD (see some neighbour thread).
Did you use the fixed libGAP spkg from #14323 [1]?
At which point of docbuilding does it "stop"? Does it reproducibly
"stop" at the same point? Did you try running 'sage --docbuild ...' (as
opposed to 'make doc') instead?
-leif
Does somebody have an idea what happens? What I could try to test?
Snark on #sagemath
[1] http://trac.sagemath.org/sage_trac/ticket/14323
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
