It definitely is the case: dynamic library locations are hardcoded via the rpath facility.
https://github.com/sagemath/binary-pkg I already mentioned builds in a special location and provides a script that edits binaries, replacing the rpaths to the one needed. On Thursday, March 9, 2017 at 8:35:16 PM UTC, Gere Mia wrote: > > This might have something to do with my having built Sage in /tmp and > moved it to /opt. It ran just fine where I built it. > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
