Sorry for the noise. It was not recompiling wrap.cc since it found an
error in compiling mwrank.pyx, which it does first, and then quit.
the error in mwrank.pyx was that I had introduced a new function but
had only put in its implementation code, not a separate declaration.
Well, I am learning!
On 3 February 2010 11:54, Martin Albrecht wrote:
> On Wednesday 03 February 2010, John Cremona wrote:
>> I'm making some changes to the eclib spkg (a bug fix and some other
>> useful stuff) which mean that I have to make changes in
>> sage/libs/mwrank. I am finding that after making edits to file
On Wednesday 03 February 2010, John Cremona wrote:
> I'm making some changes to the eclib spkg (a bug fix and some other
> useful stuff) which mean that I have to make changes in
> sage/libs/mwrank. I am finding that after making edits to files in
> that directory, "sage -b" does not seem to resul
I'm making some changes to the eclib spkg (a bug fix and some other
useful stuff) which mean that I have to make changes in
sage/libs/mwrank. I am finding that after making edits to files in
that directory, "sage -b" does not seem to result in the rebuilt sage
knowing about the changes made.
I ca
