On Mar 11, 2016, at 10:08 , Christopher Maness wrote: > > >> >> Did you build or install a pre-built Sage? Anything that looks sketchy in >> the system logs (open the Console app)? Are you using a notebook or >> terminal interface to sage? > > I have unpacked the binary over my old 6.6 installation. The console shows > nothing sketchy. I am running the notebook. I can try it out on the > terminal as well. > >> >> Another thought: start a fresh version of Sage in a Terminal window and see >> if that works. > > I reopened it, and now it is working in console and notebook(). —Weird
Well the weirdness depends on what went on before (and what kind of history the "kernel" keeps. Having a history of GUI rejection I have rarely used the notebook interface. Did you try before in Terminal and get that failure? >> At this point, I have no idea what could be wrong… > > Should I try recompiling if this happens in the future? I forgot how to do > that. I don't know that recompiling would fix anything, but you could try. As for building, it is fairly simple (as long as nothing goes worng :-}). I just do "make" (with a "-j" factor to build in parallel; and if it breaks, take out the "-j", or cut down the number of threads). I would consider building in a separate location, in case of breakage - you would at least have a more-or-less working sage left over. Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- While creating wives, God promised men that good and obedient wives would be found in all corners of the world. Then He made the earth round. -- -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
