> By the way, is there an easy way to keep multiple builds of sage in the
> same repo? It is extremely annoying to have to remake the whole thing every
> time I switch to another ticket.
>
Well, my personnal trick is to never checkout a branch based on an old
release. If I need to, I first merge i
I updated to beta3 and did a `make` (no `distclean`). It compiled Sage, but
it broke on the docs. After a `make doc-clean`, docs compiled ok.
Then I tried to checkout a ticket based on beta2 (#14540) and compilation
broke again. I guess this is no surprise, since, according to the
changelog, NT
try a "make distclean && make"
On Saturday, March 8, 2014 3:38:35 PM UTC, defeo wrote:
>
> After a `git pull develop`, build fails with the error below. Same
> fail on a frech clone. Same on beta3. Any ideas?
>
> Luca
>
>
> cc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -fPIC
>
After a `git pull develop`, build fails with the error below. Same
fail on a frech clone. Same on beta3. Any ideas?
Luca
cc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -fPIC
-I/home/sebsheep/sage/local/
include/singular -I/home/sebsheep/sage/local/include/factory
-I/home/sebsheep/s
See the "develop" git branch on the trac server. Alternatively, you can get
the source tarball at
http://boxen.math.washington.edu/home/release/sage-6.2.beta2/sage-6.2.beta2.tar.gz
Changelog:
$ git log --oneline --first-parent --author "Release Manager" HEAD
6.2.beta2 ^6.2.beta1
f59a9cb Trac
