mabshoff wrote: > > > On Apr 23, 6:23 am, "Dr. David Kirkby" <david.kir...@onetel.net> > wrote: >> mabshoff wrote: >>> Hello, > > <SNIP> >> Hi Michael, > > Hi David, > >> As Sage on Solaris needs a custom tool chain, could a script be provided >> that builds that tool chain from a full (but fresh) installation of the >> latest version of Solaris, which is Solaris 10 update 6? > > Maybe, I don't know if it will happen in time for 4.0. But I have > binary packages for the toolchain. > >> In principle something like >> >> #!/bin/sh >> /usr/sfw/bin/wgethttp://www.somewhere.com/gcc-a.b.c.tar.gz >> /usr/sfw/bin/wgethttp://www.somewhere.com/gmake-e.g.g.tar.gz >> ... >> /usr/sfw/bin/gtar xf gcc-a.b.c.tar.gz >> >> To say >> >> "It builds on skynet" >> >> is not too helpful to people. > > Well, it is helpful to the people who pay me and it will work on the > T2000 we will be hosting the notebook on. > >> Whereas you if you could say "Various versions of gcc, make, etc cause >> problems with Sage, but if you use this script on a fresh full >> installation of Solaris 10 update 6, you will have all the tools >> necessary." > > See http://wiki.sagemath.org/solaris/toolchain for details. > >> As far as I know (but are NOT 100% sure), a full install of Solaris 10 >> update 6 on SPARC includes >> >> * GNU tar (version 1.14) >> * gcc (version 3.4.3) >> * wget (version 1.10.2) >> * GNU make (version 3.80, under the name 'gmake') >> >> All those are in /usr/sfw/bin > > I know, they are too broken to build Sage reliably, especially the > linker. We also don't support using g77 as a Fortran compiler at the > moment, but we will again in the future. > >> As it is necessary to build a later gcc, then I assume that will be one >> of the steps in the script. If building gcc needs to be done in two >> stages (i.e. build version 4.1 from 3.4.2, then use 4.1 to build 4.3), >> then that too could be scripted. >> >> Once someone has a suitable tool chain, they might have some hope of >> making a useful contribution on the rest of the Solaris issues. > > OK. Not that for gcc 4.2.2 the gfortran creates completely broken code > on Sparc, so the only toolchain I will be using is the one specified > above since it is well tested by me.
But it's pretty much irrelavent if 4.2.2 creates buggy fortan - I assume you have found at least one version which does not. But the point is, whatever method you use to create a tool chain could be scripted. I doubt that script would be that long either. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
