On Sat, Aug 1, 2009 at 12:22 PM, Jason Moxham<ja...@njkfrudils.plus.com> wrote:
>
>
> Hi
>
> So are you saying that the compilers on T2 are broken in 64bit mode ? or just
> sage is broken ? or just mpir ? or dont we know?

Nobody has attempted to port Sage to 64-bit Solaris (well, since 2005
when we last tried).  I don't think anything else in particular is
supposed to be broken.

>
> I remember testing  ABI=32bit before and it passed , but as T2 is a 64bit
> machine , I regarded this as not exactly what we want  , we want 64bit
> goodness :)

Yes.  But for now all recent Solaris porting effort on Sage has gone into
making a 32-bit build that works...

>
> Thanks
> Jason
>
> On Friday 31 July 2009 14:25:02 David Kirkby wrote:
>> The version of MPIR in Sage does build on t2 properly with
>> /usr/local/gcc-4.2.4-sun-linker/bin/gcc. In fact, it builds with all
>> versions of gcc on t2.
>>
>> I can't say about the version in trunc, and cant easily check myself
>> at the minute.
>>
>> 2009/7/31 Jason Moxham <ja...@njkfrudils.plus.com>:
>> > Building mpir svn trunk (which for the Sun's is the same as mpir-1.2.2)
>> >
>> > ./configure && make -j && make -j check
>> >
>> > ld.so.1: t-modlinv: fatal:
>> > /usr/local/gcc-4.2.4-sun-linker/lib/libgcc_s.so.1: wrong ELF class:
>> > ELFCLASS32
>> > /bin/bash: line 1: 25188 Killed                  ${dir}$tst
>> > FAIL: t-modlinv
>>
>> I suggest you try ./configure ABI=32
>>
>>
>> You are mixing 32 and 64-bit objects. There is little chance of Sage
>> building in 64-bit mode on Solaris at the minute. So just use 32-bit
>> mode.
>>
>> Dave
>>
>>
>
>
> >
>



-- 
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to