On Tuesday, May 27, 2014 6:02:20 AM UTC+2, Ralf Stephan wrote:
I have reread this thread and I'm asking myself if the ecl upgrade
shouldn't have simply bumped the package-version.txt of maxima at
patchlevel, thus forcing a rebuild. I mean the author of that ticket surely
had the same
P Purkayastha wrote:
On Monday, May 26, 2014 10:08:19 PM UTC+8, leif wrote:
Nathann Cohen wrote:
Whether we should make it the default in the top-level Makefile
has been
discussed a couple of times in the past years, and IIRC most
agreed we
should do so, but so far
Ralf Stephan wrote:
John Palmieri recently helped me with a ticket (#16350) where the
spkg-install
of a package was changed but that was not enough to trigger the necessary
rebuild. That could be accomplished by adding '.p0' to the
package-version.txt
because patch level changes don't change the
Hello,
John Palmieri recently helped me with a ticket (#16350) where the
spkg-install
of a package was changed but that was not enough to trigger the necessary
rebuild. That could be accomplished by adding '.p0' to the
package-version.txt
because patch level changes don't change the actual
On Tue, May 27, 2014 at 5:11 PM, kcrisman kcris...@gmail.com wrote:
By the way, this still hasn't made it to
http://sagemath.org/mirror/src/changelogs/sage-6.2.txt - I'm cc:ing Harald.
I'm aware of that. It will happen in the next days, I promise ;-)
Harald
--
You received this message
On Tuesday, May 27, 2014 11:38:25 AM UTC-4, Harald Schilly wrote:
On Tue, May 27, 2014 at 5:11 PM, kcrisman kcri...@gmail.com javascript:
wrote:
By the way, this still hasn't made it to
http://sagemath.org/mirror/src/changelogs/sage-6.2.txt - I'm cc:ing
Harald.
I'm aware of that.
Finally had time to upgrade to 6.2 via git pull and make...
File matrix_integer_dense.pxd, line 10, in init
sage.matrix.matrix_modn_sparse (sage/matrix/matrix_modn_sparse.c:16407)
File linbox.pxd, line 7, in init sage.matrix.matrix_integer_dense
(sage/matrix/matrix_integer_dense.c:43253)
That's unfortunate. Indeed, I do not have libntl.0.dylib, just
libntl.3.dylib and libntl.dylib. And yes, this was from a working 6.1.1
:-) All on OS X 10.7.5 with usual tools. Is this another
SAGE_UPGRADING=yes (I don't - yet - have it set) thing?
Yes and no (since it's the
kcrisman wrote:
That's unfortunate. Indeed, I do not have libntl.0.dylib, just
libntl.3.dylib and libntl.dylib. And yes, this was from a
working 6.1.1
:-) All on OS X 10.7.5 with usual tools. Is this another
SAGE_UPGRADING=yes (I don't - yet - have it set) thing?
Thanks, I think I came to this same conclusion eventually. Now I just have
to figure out why building doc also seems to fail more than I want...
[calculus ] Exception occurred:
[calculus ] File ecl.pyx, line 337, in sage.libs.ecl.ecl_safe_eval
(sage/libs/ecl.c:4352)
[calculus ] RuntimeError:
Hello !
[calculus ] Exception occurred:
[calculus ] File ecl.pyx, line 337, in sage.libs.ecl.ecl_safe_eval
(sage/libs/ecl.c:4352)
[calculus ] RuntimeError: ECL says: Module error: Don't know how to REQUIRE
MAXIMA.
[calculus ] The full traceback has been saved in
Nathann Cohen wrote:
Hello !
[calculus ] Exception occurred:
[calculus ] File ecl.pyx, line 337, in sage.libs.ecl.ecl_safe_eval
(sage/libs/ecl.c:4352)
[calculus ] RuntimeError: ECL says: Module error: Don't know how to REQUIRE
MAXIMA.
[calculus ] The full traceback has been saved in
On Tuesday, May 27, 2014 7:31:37 PM UTC+1, kcrisman wrote:
I've had more trouble with building doc since the git switch than I can
shake a stick at.
We intentionally made warnings into errors that break doc build. The docs
didn't build before either, you just didn't notice.
--
You
13 matches
Mail list logo
