On 2013-01-12, Volker Braun <[email protected]> wrote:
> ------=_Part_232_20876780.1357986403573
> Content-Type: text/plain; charset=ISO-8859-1
>
> When you compiled Sage, there was a limits.h somewhere that the bootstrap 
> compiler used.
>
> The gcc limits.h tries to include that old limits.h at the end, but this 
> fails in your case. Did you uninstall anything between compiling Sage and 
> trying to compile the Cython class now? Where else is limits.h in your 
> filesystem? Whats the output of "sage -sh && cpp -v"
>
looks like this happens with a binary install (I am guessing by looking
at the path /Applications/sage/...).

And this means that not all the necessary headers got packaged
when it was being made.
>
>
> On Saturday, January 12, 2013 5:21:42 AM UTC, Roger Frye wrote:
>>
>> In file included from 
>> /Applications/sage/local/bin/../lib/gcc/x86_64-apple-darwin12.2.0/4.6.3/include-fixed/syslimits.h:7:0,
>>                  from 
>> /Applications/sage/local/bin/../lib/gcc/x86_64-apple-darwin12.2.0/4.6.3/include-fixed/limits.h:34,
>>                  from 
>> /Applications/sage/local/include/python2.7/Python.h:19,
>>                  from _Users_rogerfrye_Target_Sage_hello_spyx_1.c:4:
>> /Applications/sage/local/bin/../lib/gcc/x86_64-apple-darwin12.2.0/4.6.3/include-fixed/limits.h:169:61:
>>  
>> fatal error: limits.h: No such file or directory
>> compilation terminated.
>> error: command 'gcc' failed with exit status 1
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
Visit this group at http://groups.google.com/group/sage-support?hl=en.


Reply via email to