On Jan 9, 2009, at 5:47 PM, Michael Abshoff wrote: > Stefan Behnel wrote: >> Dag Sverre Seljebotn wrote: >>> I don't have time for fixing it, but old_temp in NewTempsExprNode >>> was >>> introduced solely to do "print self.old_temp" during debugging. >>> Sorry, >>> there should have beena comment. >> >> I fixed the crash (but not the underlying temp problem). > > Thanks > >> You should at >> least get a meaningful error message out of it now. > > Now the first file in the Sage library builds, but the second one from > 3.2.3 fails:
[...] > RuntimeError: no temp, but release requested in CoerceToTempNode > > I am not quite sure what to do next, but I am hoping RobertWB or > somwbody else has an idea what the problem might be :) OK, I looked into this and got Cython to work through the entire Sage library. It has issues compiling http://hg.sagemath.org/sage-main/file/b0aa7ef45b3c/sage/combinat/ matrices/dancing_links.pyx http://hg.sagemath.org/sage-main/file/b0aa7ef45b3c/sage/combinat/ matrices/dancing_links_c.h sage/combinat/matrices/dancing_links_c.h: In member function ‘column* dancing_links::smallest_column()’: sage/combinat/matrices/dancing_links_c.h:73: error: ‘set’ was not declared in this scope sage/combinat/matrices/dancing_links_c.h:73: error: expected primary- expression before ‘*’ token sage/combinat/matrices/dancing_links_c.h:73: error: expected primary- expression before ‘>’ token sage/combinat/matrices/dancing_links_c.h:73: error: ‘seenColumns’ was not declared in this scope and I don't know enough C++ to diagnose the error message. Any ideas? - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
