There's a fully built MPIR in my home directory. The include (gmp.h)
is in /home/wbhart/mpir-trunk/ and the libraries (libgmp.*) are in /
home/wbhart/mpir-trunk/.libs

Bill.

On 6 June, 17:13, William Stein <wst...@gmail.com> wrote:
> On Sat, Jun 6, 2009 at 9:09 AM, William Stein<wst...@gmail.com> wrote:
> > On Sat, Jun 6, 2009 at 8:45 AM, Dr. David Kirkby<david.kir...@onetel.net> 
> > wrote:
> >> William Stein wrote:
>
> >>> -bash-3.00$ cat /etc/release
> >>>                       Solaris 10 1/06 s10s_u1wos_19a SPARC
> >>>           Copyright 2005 Sun Microsystems, Inc.  All Rights Reserved.
> >>>                        Use is subject to license terms.
> >>>                           Assembled 07 December 2005
>
> >>> whereas on t2.math:
>
> >>> wst...@t2:~$ cat /etc/release
> >>>                       Solaris 10 8/07 s10s_u4wos_12b SPARC
> >>>           Copyright 2007 Sun Microsystems, Inc.  All Rights Reserved.
> >>>                        Use is subject to license terms.
> >>>                            Assembled 16 August 2007
>
> >> Hi,
>
> >> the first of those machines is update 1, so quite old and should any binary
> >> build on that, it should run on t2 too.
>
> >> But William said on sage-devel that the toolchain could have been built on
> >> one of two machines (mark or mark2). Since they both have the same kernel
> >> patch, I assume they are both Solaris 10 update 1 (07/2005). In that case,
> >> it proves me wrong about the Solaris version being the problem. But perhaps
> >> you can just confirm that.
>
> > I have just confirmed that mark and mark2 have identical Solaris installs.
> > So I guess that wasn't the problem.
>
> >> Either way, that fortran compiler is definitely a problem on t2, as even a
> >> simple example fortran program I downloaded from the web caused the 
> >> internal
> >> error, so it's not some exotic code in Sage that is exploiting an obscure
> >> compiler bug.
>
> >> Anyway, the build of gcc-4.4.0 seems to be going ok (about an hour 
> >> compiling
> >> now!), so hopefully that will help matters.
>
> > Yep, gcc takes a long time to build.
>
> > There is also a GCC-4.2.1 Sage spkg that Michael made nearly two years
> > ago.  It's in the Sage experimental package repo.  I'll try that on t2
> > and see what happens:
>
> > wst...@t2:~/t2/sage-4.0$ ./sage -i gcc-4.2.1
>
> > (I doubt it will work, but we'll see...)
>
> It fails with:
>
> checking whether compiler driver understands Ada... no
> checking how to compare bootstrapped objects... cmp $$f1 $$f2 16 16
> checking for correct version of gmp.h... yes
> checking for correct version of mpfr.h... buggy version of MPFR detected
> checking for any version of mpfr.h... no
> configure: error: GMP 4.1 and MPFR 2.2.1 or newer versions required by fortran
> Error configuring gcc
>
> real    0m15.238s
> user    0m0.874s
> sys     0m1.589s
> sage: An error occurred while installing gcc-4.2.1
>
>
>
> > David, if you are interested at all in making a new Sage GCC spkg (for
> > gcc-4.4.0), which works on Solaris (in addition to other OS's), that
> > would be a greatly appreciated contribution you could make to the Sage
> > project.   You can get the gcc-4.2.1 spkg here, if you want to see how
> > it is constructed:
>
> >http://sagemath.org/packages/experimental/
>
> > William
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send 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