Le 25/03/2013 17:18, leif a écrit :
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.
From personal experience, even happier!
* What Sage version is this based on? (And which spkgs did you "replace"
by system ones? Versions?)
It is based on sage 5.8, and I replaced 3/4 of spkgs with system ones,
so the list is daunting.
* What platform (OS, CPU)?
OS is debian/unstable with experimental packages and even more
experimental packages -- or that wouldn't have been experiments ;-)
CPU is AMD Athlon(tm) 64 X2 Dual Core Processor 5200+.
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).
I remember Stephen's problems, but if I remember well, the idea was that
it was a freeBSD-specific issue.
But now if you think that is the same thing, there's also:
- John Cremona's problem with processes which were overtaxing his box ;
- my own problem with running "make ptestlong" on my small arm box, with
processes which were overtaxing the poor thing.
Did you use the fixed libGAP spkg from #14323 [1]?
No, as I wasn't aware of this -- I'm definitely going to give it a try soon!
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?
Yes. No, but as far as I know 'make doc' calls 'sage --bocbuild' which
calls 'builder.py' (I saw them in ps -ef).
Let's play with the libgap spkg!
Snark
--
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.
