On Mon, 21 Sep 2015, Jeroen Demeyer wrote:
Your workflow should look like:
1) checkout ticket or branch
2) make build (or make doc-clean; make)
If you're skipping step 2, it's not surprising that bad things happen.
OK. Before it has more often worked with just ./sage -b and I think that
als
On 2015-09-21 15:04, Jori Mäntysalo wrote:
I don't know exactly what has happened, but at least on my systems
compiling is more frequently needed, i.e. sage -b is not enough.
Did you run "make" before (or "make build" if you don't want to wait for
the doc)?
You can use "./sage -b" if, since
On Mon, 21 Sep 2015, Jeroen Demeyer wrote:
Three times is surprising, are you sure you counted correctly? I can
understand 2 (once for the toolchain, once for the package itself), but
3 is a bug. I've just tried with the latest branch at #12103, and I see
"make configure" only twice.
I don't
On 2015-09-21 11:37, Simon King wrote:
Hi!
It seems that in the latest beta there was a change in "sage -i"
Certainly, see
https://groups.google.com/forum/#!topic/sage-devel/nLDOLvjKp3A
First it does make -j2 configure.
Then, it does make -j2 configure!
Then, it does make -j2 configure!!
Th
When complaining about a command, could you mention the *exact* command
you're talking about. I assume it's not just "sage -i"?
--
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
Hi!
It seems that in the latest beta there was a change in "sage -i" that I
find rather annoying: First it does make -j2 configure. Result: Nothing
to (re)build / all up-to-date. Which takes a couple of seconds
Then, it does make -j2 configure! Result: Sage build/upgrade complete!
Which again tak
