Op vrijdag 21 november 2014 04:34:44 UTC+1 schreef Nils Bruin: > > On Thursday, November 20, 2014 7:10:15 PM UTC-8, Bozh wrote: >> >> Are these warnings signs that maxima is still compiling itself every time >> I started? >> > It looks like Peter correctly identified the problem. According to his > assessment, Maxima compiles *some code* upon startup, but not all of maxima. > > >> Since these problems seem to be unique only on my mac (and the weird >> non-existence of CLT in Xcode), can I assume that the problem actually lies >> in my OSX or Xcode? >> > The fact that maxima tries to compile something is not unique to your mac. > The fact that the compilations failed was something relatively specific to > your mac, but not unique to it. Peter sketched a system where it didn't > work either. > > Hopefully, Peter will patch the maxima shipped with sage so that we avoid > the compilation. Then probably the next sage release will not have this > compilation issue anymore. In the longer run, hopefully the maxima people > find a way around compiling some code at init-time. Then we can remove our > patched behaviour we're going to need in the mean time. > I opened a ticket for this and am now testing a patch: http://trac.sagemath.org/ticket/17375
Peter -- 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 http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
