On Saturday, May 7, 2016 at 5:46:20 PM UTC+2, William wrote: > > I read that github page, but I don't know what binary-pkg actually > does.
It compiles Sage in a long directory path. > For context, I used to (1) build a copy of Sage, (2) possibly > customize it, then (3) type > > ./sage -bdist <stuff> > > to make a binary from it. > And then (4) the bundled gmp/readline/... would segfault your system gcc/bash/.., making it totally unusable. Unless you were lucky enough to use one of the most popular distros, where we would work around that by picking the right versions of libraries to not conflict. Then Apple disabled the DYLD_LIBRARY_PATH hack, so OSX became overnight one of the affected platforms where the binaries did not work. > > What does this binary-pkg program do? Does it package up an existing > Sage install? If so, how do you specify which sage install it > packages? Yes, I read over the yaml file but couldn't figure it out. > You edit the repository: https://github.com/sagemath/sage.git branch: develop to point to the repo/branch that you want to build -- 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.
