> > >> $ export MAKE="make -j3" >> $ make >> <lots of new messages early on, including downloads of mpir - I was not >> expecting to need to be on the internet to build Sage, just to download the >> source> >> > > The Sage repository should not contain binary files nor non-sage specific > source code, so > naturally cloning the sage repository would not include compressed > tarballs of upstream > code. There are two ways to get a copy of sage with these files (so you > can do an offline > build): either use the source distribution that you find on sagemath > website, or run the > `make download` after cloning the source. These should both be documented > (they might > already be, but I don't know). > > Ah, I see! Now this makes sense - I'm not downloading the whole tarball, after all.
$ ./sage -b >> <many minutes of Cythonizing> >> >> ???? Didn't I JUST BUILD SAGE? Note that the ticket in question touches >> one .pyx file and doesn't even change any code - it's a nearly trivial >> documentation fix. >> > > You just built Sage 6.0, although for the ticket in question, it was based > off 6.1.beta5, so you will have > to compile any changes between 6.0 and 6.1.beta5 in addition to the nearly > trivial documentation > fix. I agree that this can be a pain when jumping around between a lot of > tickets, however using ccache > and cycache can alleviate a lot of the pain (it will not really fix this > particular rebuild, since you hadn't > ever built 6.1.beta5 before -- it would help you once you jump back to > running 6.0). > > Oh. I do like that now I don't have to know what version I built. But it was quite confusing, because I didn't even know what version it was built off of. Maybe if a few tags for development versions are passed, there could be an additional message pointing this out. I know that would be annoying to write. But that certainly explains things! >> $ ./sage -dev checkout master >> usage: sage-dev [-h] subcommand ... >> sage-dev: error: unrecognized arguments: master >> $ ./sage -dev checkout >> at least one of ticket or branch must be specified. >> > So... any hints on this? I assume that ./sage -dev checkout develop also wouldn't work the way I would hope. -- 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/groups/opt_out.
