On Tuesday, May 7, 2013 2:55:28 PM UTC-4, kcrisman wrote:
>
>
>> Anyway, I'm still having problems.  This time I got a long stack trace in 
>> the middle of the build, and then it seemed to continue until stalling 
>> after the lines,
>> [tensor   ] loading cross citations... looking for now-outdated files... 
>> none found
>> [tensor   ] no targets are out of date.
>> [history_a] loading cross citations... looking for now-outdated files... 
>> none found
>> [history_a] no targets are out of date.
>>
>
> Luckily, Sage should still function normally (this is just building 
> documentation).  Does it, or is this attached log file what happens when 
> you try to run Sage?
>

I just checked, and Sage does run, but I'm having problems, and I'm not 
sure if it's just my own ignorance or not.

If I run "./sage" and write "is_prime(2^32)" interpreter, it works.  
However, if I copy/paste a block of code from sagenb.org, the interpreter 
goes haywire.
If I run "./sage filename," it loads the file and tries to interpret it, 
but I get errors like "global name 'is_prime' is not defined."
Since I can't copy/paste my code into the local interpreter without 
problems, and I can't load it from a file, I'm kind of stuck manually 
typing it...which isn't exactly optimal.

Any suggestions?
 

>
> >  Is this a simple matter of "If it works it works, and if it doesn't it 
> doesn't," or do the official builds have the potential to interfere with 
> the packaging system on mismatched distributions?  I ask because Sage seems 
> to statically link to a large number of included packages, but you still 
> offer separate official builds for different distros, and the Fedora builds 
> are about 50% larger than the Ubuntu builds for some reason.
>
> They should not interfere at all, though once in a while something 
> hardcoded gets picked up incorrectly.   Sage, as a binary downloaded, 
> should not be linking to the user versions of basically anything, though it 
> might use your supplied gcc and a few other things for building.  The 
> different builds for different distros are because things are just that 
> picky in the Linux world - I don't get it, either, but I don't have Linux.
>

Thanks, that's good to know.   Any idea why the Fedora build is something 
like 50% larger?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to