After upgrading to El Capitan yesterday my sage ( v6.8 compiled from source) stopped working and I figured out that DYLD_LIBRARY_PATH and LD_LIBRARY_PATH are no longer supported by default due to SIP (system integrity protection) and rootless which are no turned on by default. After disabling rootless (boot into recovery mode with CMD+R and run 'csrutil disable' from command line) everything works for me. You can try and see if this also works for the downloaded binary distributions. As a temporary measure this might be ok but in the long run something probably have to change with the install process, e.g. rpaths as suggested by others.
Fredrik On Thursday, October 1, 2015 at 3:25:00 PM UTC+1, Thomas Kahle wrote: > > This is probably going to escalate with the public release of El Capitan. > I upgraded, and I have no local sage anymore. What can we do? I don't want > to use sage math cloud, at least not always. > > On Friday, September 11, 2015 at 10:02:36 AM UTC+2, Volker Braun wrote: >> >> Looks like Apple kept the new behavior of DYLD_* environment variables >> and they are not passed down to launched interpreters. Hence sooner or >> later we crash with symbol not found as libraries can't be located. Really >> we should have switched to rpaths years ago, this would have saved so much >> pain. Also would explain why homebrew and friends didn't trip over that. >> Don't know of any workaround on 10.11 besides sourcing sage-env whenever a >> subshell is launched. >> >> >> >> On Friday, September 11, 2015 at 4:48:25 AM UTC+2, François wrote: >>> >>> Hum, that symbol is in libpython2.7.dylib, operator.so is not linked to >>> that library. >>> I am guessing it is supposed to be dlopen-ed from python which would >>> supply >>> the symbol. I suspect python will need patching. >>> Can you start python from a sage shell? >>> >>> François >>> >>> > On 11/09/2015, at 14:40, Juan Luis Varona <juanlui...@gmail.com> >>> wrote: >>> > >>> > >>> >> El 11 sept 2015, a las 4:24, kcrisman <kcri...@gmail.com> escribió: >>> >> >>> >> But, usually, new versions of osx can execute already compiled >>> versions of sage, and this does not happen this time. (I like to have >>> always the last version of osx in one of my computers, and I do not >>> remember this problem in the past.) >>> >> >>> >> >>> >> Yes, good point. Can you give us exactly what kind of problems you >>> encounter with the 10.10 version on 10.11? (If there are any message at >>> all.) >>> >> >>> > >>> > This is what appears in the Terminal using Sage-6.8.app (compiled for >>> osx 10.10) under osx 10.11: >>> > >>> > --------- >>> > >>> > Last login: Thu Sep 10 18:37:14 on ttys000 >>> > AirTeXano:~ jvarona$ >>> '/Applications/Sage-6.8.app/Contents/Resources/sage'/sage --notebook >>> > Traceback (most recent call last): >>> > File >>> "/Applications/Sage-6.8.app/Contents/Resources/sage/src/bin/sage-notebook", >>> line 7, in <module> >>> > import argparse >>> > File >>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/argparse.py", >>> >>> line 85, in <module> >>> > import collections as _collections >>> > File >>> "/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python/collections.py", >>> >>> line 9, in <module> >>> > from operator import itemgetter as _itemgetter, eq as _eq >>> > ImportError: >>> dlopen(/Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so, >>> >>> 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString >>> > Referenced from: >>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so >>> >>> >>> > Expected in: flat namespace >>> > in >>> /Applications/Sage-6.8.app/Contents/Resources/sage/local/lib/python2.7/lib-dynload/operator.so >>> >>> >>> > AirTeXano:~ jvarona$ >>> > >>> > ———— >>> > >>> > Juan Luis >>> > >>> > >>> > -- >>> > 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+...@googlegroups.com. >>> > To post to this group, send email to sage-...@googlegroups.com. >>> > Visit this group at http://groups.google.com/group/sage-devel. >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- 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.
