Dag Sverre Seljebotn wrote:
> Michael Abshoff wrote:
>> Dag Sverre Seljebotn wrote:
>>> Michael Abshoff wrote:
>>>> Dag Sverre Seljebotn wrote:
>>>>> Robert Bradshaw wrote:
>>>> <SNIP>
>>>>
>>>> Hi Dag,
>>>>
>>>>> Status on Sage is that these fail:
>>>>>
>>>>>          sage -t  "devel/sage/sage/libs/ntl/ntl_ZZ_pX.pyx"
>>>>>          sage -t  "devel/sage/sage/rings/integer.pyx"
>>>>>          sage -t  "devel/sage/sage/plot/plot.py"
>>>>>          sage -t  "devel/sage/sage/interfaces/maxima.py"
>>>>>
>>>>> The last two seem to be because of fragile doctests. 
>>>> Can you post the first doctest failure from each failing file?
>>> This is on Sage 3.4.1 (my own build).
>> Ok. Which compiler and host? 3.4.2 is out by the way and 4.0.alpha0 
>> should drop tonight :)
> 
> da...@boksen:~/sage/sage-3.4.1$ uname -a
> Linux boksen 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 
> x86_64 GNU/Linux
> 
> da...@boksen:~/sage/sage-3.4.1$ gcc -v
> Using built-in specs.
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v 
> --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr 
> --enable-shared --with-system-zlib --libexecdir=/usr/lib 
> --without-included-gettext --enable-threads=posix --enable-nls 
> --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 
> --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc 
> --enable-mpfr --enable-checking=release --build=x86_64-linux-gnu 
> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
> Thread model: posix
> gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)

ok, noting unusual so far.

>> Ok, changing semantics like that makes me queasy, but I assume you guys 
>> know what you are doing. It seems like a rather deep fundamental change 
>> for 0.11.1->0.11.2.
> 
> I think there's no way around it now -- unless Robert wants to make this 
> 0.12 because of this change alone, it will have to be remedied by a big 
> warning in the release notes only.

I did not mean to imply that this discussion should be reopened, just 
that some people might be a little surprised that a "minor" bug fix 
breaks their code :)

>> I have never seen this and I am pretty sure it is unrelated to Cython. 
>> If you could send me a link to the compressed install.log I could take a 
>> look. This indicates a problem with libpng.
> 
> Well the real problem is if Cython does something strange (could by 
> anything, like truncating a list or whatever) leading to this. I will 
> have to run with the original Cython first and then I'll file the issue 
> properly if it is Cython-unrelated.

Still, MPL claims that png isn't supported. If this is a Cython issue 
somewhat color me surprised.

>> In case you have a $HOME/.maxima can you move that out of the way? If 
>> you do this might explain this problem.
> 
> I don't. (I get startup timeouts too BTW.)

Ok. 3.4.1 shipped with the new clisp 2.47 which has been working out 
rather well, but there is always a compiler that breaks it. Sage 4.0 
will switch to ecl and use Maxima a whole lot less. Eventually Maxima 
won't be used for anything in Sage, but that is still some time to go.

If downgrading to the old cython does not fix your problem I am more 
than happy to look into install.log from your box to see if I can find 
the cause for the MPL png issue for example.

Cheers,

Michael


_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to