On 2014-09-04 22:38, Simon King wrote:
And how can one build the debug version? I recall that one had to export
SAGE_DEBUG=yes before building, and I had several Sage versions on my
machine, all built from sources. But now, with git, I only have *one*
Sage install. Is it possible to switch back a
On Thursday, September 4, 2014 1:35:21 PM UTC+1, Jori Mantysalo wrote:
>
> > ls -al /lib /lib64
> ls: cannot access /lib64 : No such file or directory
>
You don't have a 64-bit system, it seems.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
Hi Francesco, hi all others,
On 2014-09-04, Francesco Biscani wrote:
> Probably you know this already, but Valgrind will not normally detect
> errors related to memory allocated on the stack. If Valgrind comes out
> clean but the program crashes, I'd start looking into function-local or
> global
On Thu, Aug 28, 2014 at 07:05:10AM -0700, kcrisman wrote:
>Relevant comments.
>1) There are a number of scattered resources for getting to know Sage
>that are actually useful at the level that poster is talking about.
>San Diego State tutorials, the PREP tutorials - which I happen t
Dear coercion enthousiasts,
while working on #16931, I discovered a coercion bug for polynomials
over finite fields.
Since I absolutely know nothing about coercion, I hope somebody can have
a look at this bug:
http://trac.sagemath.org/ticket/16934
Thanks,
Jeroen.
--
You received this message
Hi Clément and all,
On Friday, August 29, 2014 10:53:18 AM UTC+2, Clement Pernet wrote:
>
> Hi,
>
> Let me clarify a few things:
> - LinBox's approach to link against numerical BLAS has never changed, and
> probably will not in the
> near future.
> - LAPACK is not BLAS: BLAS provides optimiz
Probably you know this already, but Valgrind will not normally detect
errors related to memory allocated on the stack. If Valgrind comes out
clean but the program crashes, I'd start looking into function-local or
global non-dynamic arrays.
On 4 September 2014 00:41, Dima Pasechnik wrote:
> On 2
On Wed, 3 Sep 2014, Travis Scrimshaw wrote:
Before you do so, can you tell me if that graphviz is the system (local)
install or the one using the experimental
Sage spkg (just covering all my bases here)?
I have not installed any experimental package.
Ticket: http://trac.sagemath.org/ticket/1
On Wed, 3 Sep 2014, Volker Braun wrote:
Seems that Sage's version of libgfortran clashes with what ATLAS has
been compiled with. Try a "make distclean && make" to build from a clean
slate if you haven't done so before. Also, are you compiling ATLAS or
using the system ATLAS?
I tried removin
Hi sage-devel,
Can / does the Sage project have an Apple developer account,
and a way to install betas of future releases of Mac OS X on
some machine where a few developers can test building Sage,
so that Sage is ready to ship for the new OS the day it comes
out (and even earlier for those under b
10 matches
Mail list logo
