I can run your binary-pkg <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fsagemath%2Fbinary-pkg&sa=D&sntz=1&usg=AFQjCNEnRuZWLIPZdOQL7_t0kfK9mesuvw> script after having already finished building Sage? thanks
On Thursday, March 9, 2017 at 1:48:02 PM UTC-7, Dima Pasechnik wrote: > > It definitely is the case: dynamic library locations are hardcoded via the > rpath facility. > > https://github.com/sagemath/binary-pkg > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fsagemath%2Fbinary-pkg&sa=D&sntz=1&usg=AFQjCNEnRuZWLIPZdOQL7_t0kfK9mesuvw> > > 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.
