On Nov 28, 10:21 am, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> On Nov 28, 2007, at 1:13 AM, mabshoff wrote:
>
> > Amd the following happens if I make int_fast64_t a 8 byte data type,
> > i.e. a long long in 32 bit mode. Since a int_fast64_t has to be *at
> > least* 8 byte this is the correct setting.
Hello Robert,
>
> Yes, hence its name :-)
>
I know ;)
>
>
> > ----------------------------------------------------------------------
> > | SAGE Version 2.8.14, Release Date: 2007-11-24 |
> > | Type notebook() for the GUI, and license() for information. |
> > ----------------------------------------------------------------------
>
> > Traceback (most recent call last):
> > File "/tmp/Work-mabshoff/sage-2.8.14/local/lib/python2.5/site-
> > packages/sage/all_cmdline.py", line 14, in <module>
> > from sage.all import *
> > File "/tmp/Work-mabshoff/sage-2.8.14/local/lib/python2.5/site-
> > packages/sage/all.py", line 57, in <module>
> > from sage.libs.all import *
> > File "/tmp/Work-mabshoff/sage-2.8.14/local/lib/python2.5/site-
> > packages/sage/libs/all.py", line 3, in <module>
> > import sage.libs.ntl.all as ntl
> > File "/tmp/Work-mabshoff/sage-2.8.14/local/lib/python2.5/site-
> > packages/sage/libs/ntl/all.py", line 52, in <module>
> > from sage.libs.ntl.ntl_lzz_p import ntl_zz_p as zz_p
> > File "integer_mod.pxd", line 14, in sage.libs.ntl.ntl_lzz_p
> > ValueError: sage.rings.integer_mod.NativeIntStruct does not appear to
> > be the correct type object
>
> > [This issue is raised inside Cython autogenerated code. Might it be
> > that Cython gets this wrong in general?]
>
> This means that you haven't re-compiled all the necessary files. Try
> touching the integer_mod.pxd and doing a sage -b.
Oh yes, I did. The above happened for me for the first time after I
added the above definitions to my custom stdint.h during the initial
compile. It broke Sage to my surprise, I edited stdint.h [knowing it
was wrong] and changed it back to a long and Sage starts. I changed it
back after running doctests, because I didn't capture the run time
error the first time around, did a Sage -ba and voila: the above
backtrace. I am as puzzled as you why this happens, but it seems that
this should happen way before ntl_lzz_p is imported. Maybe there is a
mismatch in that code somewhere.
Another potential issue might be that in the number of workarounds for
Sun we define int_fast64_t or its friend uint_fast64_t as a long
somewhere, but it might take a while to find that.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
