> TLDR: Don't install OSX 10.11 if you want to use Sage > > This should probably be prominently mentioned somewhere on the download pages...
> OSX 10.11 disabled DYLD_* variables for scripts, more precisely: If a > script file begins with a shebang the DYLD_* environment variables are > omitted from the set of environment variables passed to that interpreter. > So that fundamentally kills the way Sage runs on OSX. > > We either > a) always re-set DYLD_LIBRARY_PATH in each bash or Python script that > calls one of Sage's binaries, or > b) give up on DYLD/LD_LIBRARY_PATH and switch to rpath/runpath. Which we > should have done a decade ago but then nobody is listening to me ;-P Which > also means: no relocatable binaries unless your system has a tool to > rewrite the paths installed. > So if someone downloads a binary it would be useless anyway, or if they build from scratch but then move it to Applications/ it would be useless, or (presumably) both? That's not ideal at all for end users, though I guess the whole mess isn't ideal :( -- 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.
