On Thursday, 1 October 2015 11:51:04 UTC-7, Dima Pasechnik wrote: > > On Thursday, 1 October 2015 07:39:51 UTC-7, Hal Snyder wrote: >> >> On Friday, September 11, 2015 at 3:02:36 AM UTC-5, 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. >>> >>> What's involved in switching to rpaths? What would be the main >> advantages? >> > > in a nutshell, rpaths are relative paths, telling the linker to search for > extra dependencies, > written into library/executives binaries, and allow you > to avoid depending on the execution environment; apparently it's very > easy to create on > Linux, but not so on OSX, where you need to jump some hoops. > People wrote tools to fix the latter, such as > https://github.com/auriamg/macdylibbundler/ > > Thus, it would mean no more runtime linking to a wrong library due to > wrong (DY)LD_LIBRARY_PATH > and the latter doesn't work (at all?) on OSX11, as far as I understand. > > this would also mean that the Cygwin port will have to stay with LD_LIBRARY_PATH, as rpath is not supported on Cygwin.
> Dima > > >> >> >>> >>> ... >>> >>> -- 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.
