On Thursday, February 28, 2013 11:38:24 PM UTC+1, Jean-Pierre Flori wrote:
>
>
>
> On Thursday, February 28, 2013 10:41:15 PM UTC+1, Dr. David Kirkby wrote:
>>
>> On 28 February 2013 16:12, Jean-Pierre Flori <jpf...@gmail.com> wrote: 
>> > For info, I'm trying to build Sage on a Debian sparc64, and it failed 
>> > because by default gcc produces 32 bits objects but then MPIR (and MPFR 
>> and 
>> > MPC) decided to be smart enough to build as 64 bits, and then when Sage 
>> > tried to build its own GCC, which is 32 bits, it failed... 
>> > 
>> > Exporting ABI=32 seems to calmn down MPIR, but I guess it should be 
>> like 
>> > that by default. 
>> > If I by any chance get a working 32 bit install, I'll try to give a 64 
>> bits 
>> > install a shot, and this should be triggered using SAGE64 :) 
>>
>> I can't see a lot of point running Linux on SPARC. OK, it might 
>> install and run, but it has had nowhere near the amount of testing as 
>> Solaris does, which is a very stable operating system - far more so 
>> that Linux in most cases. Linux on SPARC will get very little testing. 
>>
>> > I'll also give a shot on Solaris 10 / sparc64, but the gcc I have there 
>> is 
>> > old and MPIR complains... 
>>
> To be clear, the GCC/MPIR problem did not happen on Solaris.
It failed before complaining it could not find the prereq-1.1 untarred dir.
Strange. 

>
>> Sage has a gcc package which the gcc 3.4.3 did build last time I tried 
>> it - 6 months or so ago. My SPARC is on now doing some data collection 
>> from a vector network analyzer. I could try building the latest Sage 
>> and let you know how it gets on. 
>>
>> I'd certainly try Sage 32-bit on Solaris before attempting 64-bit. 
>> Last time I tried there was a problem with Pynac loading things it 
>> should not, and this made it impossible to build a stabe Sage on 
>> 64-bit SPARC. I think it is possible to compute 1+1, but not al alful 
>> lot else. 
>>
>> I'll download the latest Sage and give it a try. I don't have the 
>> latest Solaris on my SPARC - it Solaris 10 3/05, so about 8 years old. 
>> But given the excellent  backwards compatibility of Solaris, if Sage 
>> builds on the 2005 realease it should build on the 2013 release. 
>>
>> Dave 
>>
> I also have access to a Solaris (5.10) Sparc (ultrasparc T2+) but it 
> failed miserably unpacking the prereq spkg, so I've begun with what looked 
> easier first. 
> I'll report on that as well. 
>

-- 
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