ke
Thank you Mike. We don't have 'nosetests' as a part of Sage, but it should be
possible to write a script which just executes the first two lines.
I'll add that to Sage so we can run the matplotlib test suite.
Dave
> On 06/27/2010 08:24 AM, Dr. David Kirkby wrote:
>> M
Matplotlib is used as part of the Sage project, where we aim to run test-suites
that are part of upstream packages where possible. Someone suggested it would
be
good if we did that for Matplotlib, which we currently do not do. However, on
reading the contents of the source directory (README.txt
On 06/11/10 10:28 PM, Eric Firing wrote:
> On 06/11/2010 10:54 AM, Dr. David Kirkby wrote:
>> The latest stable (0.99.3) matplotlib builds ok on Solaris 10 03/05 on SPARC.
>>
>> However, your latest trunc release has some useful fixes, so it was
>> downloaded
>> b
The latest stable (0.99.3) matplotlib builds ok on Solaris 10 03/05 on SPARC.
However, your latest trunc release has some useful fixes, so it was downloaded
by a fellow Sage devloper. However, when I try to build this version on a Sun
Blade 1000 running Solaris 10 03/05, it presents a problem:
g hacks that are certain to break on
>>> as many systems as they fix. We just may be forced to deal with it
>>> at this point, though. (FWIW, we run Solaris here, too, but we build
>>> matplotlib on gcc). I'll comment on that bug as well and see if we
>
t
all out. There is some code I need to fix, and I will take the same course of
action. It seems more trouble than it is worth to me.
Dave
> Dr. David Kirkby wrote:
>> I was trying to build matplotlib 0.99.0 as part of Sage
>>
>> http://www.sagemath.org/
>>
>>
I was trying to build matplotlib 0.99.0 as part of Sage
http://www.sagemath.org/
on a Sun Blade 2000 workstation running Solaris 10 update 7, using the Sun
Studio compiler version 12.1 (not gcc).
CC and CXX were defined properly as C and C++ compilers, but it would appear
that the C compiler i
