On Sat, May 7, 2016 at 9:02 AM, Dima Pasechnik <dimp...@gmail.com> wrote: > Yes, I know, I was puzzled by this some time ago too. The reason for all > this mess is that in order to make > a relocatable Sage binary (more precisely, a bunch of relocateable libs etc) > that uses rpath, it has to be built at a location that will allow > pattern-matching on binaries to work (so it has to be some long and > convoluted string). > Thus your usual directory where you build Sage won't work.
Thank you for the explanation. I wish that instead of breaking all the existing stuff, we had just made the new parts and left the old as an option. (I realize the proper rpath support is useful for OS X, etc., but it is a pain.) Definitely one very useful aspect of Sage, which I had worked very hard to make, is completely gone now. -- Wiliam > > Dima > > On Saturday, May 7, 2016 at 4:46:20 PM UTC+1, William wrote: >> >> On Sat, May 7, 2016 at 2:00 AM, Volker Braun <vbrau...@gmail.com> wrote: >> > The sage script in your PATH is outdated: >> > >> > $ ./sage -advanced | grep bdist >> > $ egrep -r bdist src/ >> > $ >> > >> > The way to build binary (relocatable) packages is >> > https://github.com/sagemath/binary-pkg, which says: >> > >> > git clone https://github.com/sagemath/binary-pkg.git >> > cd binary-pkg >> > make bdist-sage-linux # If you are on Linux >> > make bdist-sage-osx # If you are on OSX >> > ls dist/ # Built binaries will be in this directory >> >> I read that github page, but I don't know what binary-pkg actually >> does. The docs don't answer my questions. >> >> 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. >> >> 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. >> >> >> <frustration> >> I am sad that I can't copy existing sage installs, and I'm now even >> sadder that I can't type "./sage -bdist" anymore. Two of the most >> important things for making sage dev easy for people are gone. If I >> had the time, I would make a fork of Sage that restored exactly this >> behavior then always merge it into sage... >> </frustration> >> >> William >> >> >> > >> > >> > >> > On Saturday, May 7, 2016 at 2:05:00 AM UTC+2, William Stein wrote: >> >> >> >> Either my build is completely hosed, or "sage -bdist" is completely >> >> broken: >> >> >> >> salvus@compute7-us:/projects/sage/sage-develop$ time ./sage -bdist tmp >> >> sage-run received unknown option: -bdist >> >> usage: sage [options] >> >> Try 'sage -h' for more information. >> >> salvus@compute7-us:/projects/sage/sage-develop$ sage -advanced|grep >> >> dist >> >> Making Sage packages or distributions: >> >> -bdist <tmpdir> -- build a binary distribution of Sage >> >> -sdist -- build a source distribution of Sage >> >> salvus@compute7-us:/projects/sage/sage-develop$ ls >> >> aclocal.m4 bootstrap config config.status configure.ac >> >> local m4 README.md src VERSION.txt >> >> autom4te.cache build config.log configure COPYING.txt >> >> logs Makefile sage upstream >> >> >> >> --- >> >> >> >> Also, even if bdist worked, I don't understand the docs. What's >> >> <tmpdir>??!?? Where does the bdist actually go?? It used to go in a >> >> directory SAGE_ROOT/dist, I think. >> >> >> >> William >> >> >> >> >> >> On Fri, May 6, 2016 at 2:42 AM, Eric Gourgoulhon <egourg...@gmail.com> >> >> wrote: >> >> > As it stands, symbolic calculus is quite severely broken in Sage 7.2: >> >> > making >> >> > any assumption on a symbolic variable turns it into an integer. For >> >> > instance >> >> > assume(x>0) yields sin(pi*x)=0. This has many undesirable >> >> > consequences >> >> > and >> >> > users will probably complain a lot. Fortunately a fix is provided by >> >> > the >> >> > upgrade to the latest version of pynac, which is proposed in #20475. >> >> > I >> >> > am >> >> > reviewing this ticket and IMHO it should be merged before releasing >> >> > 7.2. >> >> > >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups >> >> > "sage-release" group. >> >> > To unsubscribe from this group and stop receiving emails from it, >> >> > send >> >> > an >> >> > email to sage-release...@googlegroups.com. >> >> > To post to this group, send email to sage-r...@googlegroups.com. >> >> > Visit this group at https://groups.google.com/group/sage-release. >> >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> >> >> >> >> -- >> >> William (http://wstein.org) >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "sage-release" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to sage-release...@googlegroups.com. >> > To post to this group, send email to sage-r...@googlegroups.com. >> > Visit this group at https://groups.google.com/group/sage-release. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> William (http://wstein.org) > > -- > 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. -- William (http://wstein.org) -- 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.
