Volker Braun wrote:
We need the whole log, not just the last two lines.
And I'd need some context to understand what you're replying to. ;-)
Even in threaded view, it's unclear which lines you're referring to, as
John didn't quote any output in the message you replied to. (Not even
the quot
OK instead of attaching to a running process we'll strace it from the start.
strace -o builddoc.log -f -ff python /home/jec/sage/src/doc/common/builder.py
--no-pdf-links all html
It should produce log files for all the processes created in builddoc.log.$pid
and we'll want these.
Past bedtime in
We need the whole log, not just the last two lines.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this gr
On 16 April 2014 12:56, John Cremona wrote:
> On 16 April 2014 12:49, Francois Bissey
> wrote:
>> Hum, yes the parent process is listening for the child but the child seem to
>> be
>> mute. Very difficult to do that kind of stuff over email, we'd need to find
>> what
>
> I know -- and your help
On 16 April 2014 12:49, Francois Bissey
wrote:
> Hum, yes the parent process is listening for the child but the child seem to
> be
> mute. Very difficult to do that kind of stuff over email, we'd need to find
> what
I know -- and your help in debugging this is appreciated!
> look that process
Hum, yes the parent process is listening for the child but the child seem to be
mute. Very difficult to do that kind of stuff over email, we'd need to find what
look that process and I cannot think of anything simple to do that...
Instead of using make, go into a sage shell (./sage -sh) and start
On 16 April 2014 12:36, Francois Bissey
wrote:
> Find the PID of the process and then do "strace -p PID" to see what exactly
> it is
> doing.
> Warning you'll probably get a ton of output that means nothing to you.
>
OK, I did that after restarting the make (since I had killed the 99% process).
On 16 April 2014 12:27, John Cremona wrote:
> On 16 April 2014 12:18, Francois Bissey
> wrote:
>> Is it even from this attempt to build the doc or an earlier attempt?
>
> It's this attempt -- I verified that by Ctrl-C-ing the make, when
> these processes disappeared, then running make again. The
Find the PID of the process and then do "strace -p PID" to see what exactly it
is
doing.
Warning you'll probably get a ton of output that means nothing to you.
François
On 16/04/2014, at 23:27, John Cremona wrote:
> On 16 April 2014 12:18, Francois Bissey
> wrote:
>> Is it even from this attem
On 16 April 2014 12:18, Francois Bissey
wrote:
> Is it even from this attempt to build the doc or an earlier attempt?
It's this attempt -- I verified that by Ctrl-C-ing the make, when
these processes disappeared, then running make again. The four
processes started up and now the situation is as
Is it even from this attempt to build the doc or an earlier attempt?
On 16/04/2014, at 23:13, John Cremona wrote:
> Thanks for the suggestions: at the bottom of the tree, it is running 4 copies
> of
>
> python /home/jec/sage/src/doc/common/builder.py --no-pdf-links all html
>
> One of the fou
Thanks for the suggestions: at the bottom of the tree, it is running 4 copies of
python /home/jec/sage/src/doc/common/builder.py --no-pdf-links all html
One of the four is using 99% of a CPU, the others none.
John
On 16 April 2014 12:01, P Purkayastha wrote:
>
>
>
> On Wed, Apr 16, 2014 at 6:5
On Wed, Apr 16, 2014 at 6:56 PM, John Cremona wrote:
>
> Still no success with make doc. I have no idea what it is doing when
> it stops outputting (to either the screen of log file). There are no
> error messages, it just stops.
>
> John
>
Try running htop and look at the tree view to see what
Is there still a process going on in the background? Something that could be
attached to tools like strafe or gdb.
François
On 16/04/2014, at 22:56, John Cremona wrote:
> On 15 April 2014 20:12, John Cremona wrote:
>> On 15 April 2014 20:00, Volker Braun wrote:
>>> Scroll up, the real error sh
On 15 April 2014 20:12, John Cremona wrote:
> On 15 April 2014 20:00, Volker Braun wrote:
>> Scroll up, the real error should be somewhere.
>>
>> On Tuesday, April 15, 2014 7:42:37 PM UTC+1, John Cremona wrote:
>>>
>>> I am having trouble building the docs here: after (git checkout
>>> develop;
On 2014-04-16 10:33, P Purkayastha wrote:
I had trouble with building the docs too. But after a "make doc-clean",
the next "make doc" proceeded correctly. make was run as "make -j2"
(that's all the compute power I got on this machine :P)
What caught my eye during the upgrade was the very high nu
I had trouble with building the docs too. But after a "make doc-clean", the
next "make doc" proceeded correctly. make was run as "make -j2" (that's all
the compute power I got on this machine :P)
What caught my eye during the upgrade was the very high number of gcc
warnings, for example "local
On 15 April 2014 20:00, Volker Braun wrote:
> Scroll up, the real error should be somewhere.
>
> On Tuesday, April 15, 2014 7:42:37 PM UTC+1, John Cremona wrote:
>>
>> I am having trouble building the docs here: after (git checkout
>> develop; git pull trac develop; make) Sage builds fine but th
Scroll up, the real error should be somewhere.
On Tuesday, April 15, 2014 7:42:37 PM UTC+1, John Cremona wrote:
>
> I am having trouble building the docs here: after (git checkout
> develop; git pull trac develop; make) Sage builds fine but there was
> an error message building docs, so I did
I am having trouble building the docs here: after (git checkout
develop; git pull trac develop; make) Sage builds fine but there was
an error message building docs, so I did make doc-clean and make
again. then it stuck dead (for several hours, I was not watching) at
some point, so I killed it wi
See the updated "develop" branch or download the source tarball:
http://boxen.math.washington.edu/home/release/sage-6.2.beta8/sage-6.2.beta8.tar.gz
f55df77 Updated Sage version to 6.2.beta8
0a5f3eb Trac #15882: Implement a catalog for crystals
c1b3522 Trac #15836: BasisMatroid.circuits() returns
21 matches
Mail list logo
