Hey Amit, From a quick look at the commit log, I think you've updated Sage, but haven't rebuilt the spkgs, of which there are changes in the Sage code which require those to be rebuilt. The code on the ticket has nothing to do with PARI, so I expect you will experience on "develop" (note, not "master") as well. What I'd suggest doing is going into $SAGE_ROOT and running "make build". If that doesn't work, there's always the nuclear option "make distclean && make".
Best, Travis On Wednesday, September 24, 2014 4:18:49 PM UTC-5, Amit Jamadagni wrote: > > Hello everyone, > I have been working on the knot theory module. I have pushed all my > work onto github. Recently I created a ticket #17030, and have added the > trac details. Here is what I get when I do a > git remote -v > origin https://github.com/amitjamadagni/sage (fetch) > origin https://github.com/amitjamadagni/sage (push) > trac git://trac.sagemath.org/sage.git (fetch) > trac g...@trac.sagemath.org:sage.git (push) > > Now I used to use the following procedure to push my work onto github. > Changes ---> build sage --->> test the results --->> commit and then push > > After I have added the trac details, when I build sage it takes a lot more > time when compared to the previous time which I used to do before > committing the changes onto github. And sage does not build completely > instead it ends with the following error : > > error: command 'gcc' failed with exit status 1 > build/cythonized/sage/libs/pari/handle_error.c: In function > ‘__pyx_f_4sage_4libs_4pari_12handle_error__pari_handle_exception’: > build/cythonized/sage/libs/pari/handle_error.c:1046:32: error: ‘e_STACK’ > undeclared (first use in this function) > build/cythonized/sage/libs/pari/handle_error.c:1046:32: note: each > undeclared identifier is reported only once for each function it appears in > build/cythonized/sage/libs/pari/handle_error.c:1107:32: error: ‘e_USER’ > undeclared (first use in this function) > > This has happened with when I do the above activity on my local machine as > well when I tried it on the cloud. > > Here are my doubts: > 1. How do I go about resolving the above issue. > 2. I checkout onto the required branch my doing git trac checkout 17030. > Do the changes reflect both in the local branch on github as well as the > current branch?? > > Thanks. > > -- 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. For more options, visit https://groups.google.com/d/optout.
