Yes, but in the absence of an achieved utopia, is there something we can do here? I see that sage-env already has a lot of LD_LIBRARY_PATH hacking in it. Might be good to design a system for regularizing this, and moving all this hacking to that system.
My solution has been to add Python code to detect this, and put out a warning to the user, telling them to add the required LD_LIBRARY_PATH setting to their sagerc file. Somewhat unsatisfactory. Bill On Monday, September 21, 2015 at 10:49:05 AM UTC-7, Jeroen Demeyer wrote: > > On 2015-09-21 19:23, Bill Janssen wrote: > > On OS X, The CasADi subsystem now installs its dynamic > > libraries in a subdirectory of JModelica, a subdirectory which then has > > to be put on the LD_LIBRARY_PATH the Python interpreter is run with > That is clearly an issue with the build system. Instead of requiring > Sage to change sage-env, it would be better to report this problem > upstream. Libraries should be installed in the standard places, such > that no special LD_LIBRARY_PATH hacks are needed. > -- 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.
