On 17 November 2010 23:56, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > Thanks for taking care of this ! > > I was just trying to run tests on Solaris for the next Ecl and Maxima > spgk's... > > I'll try downlaoding your lib tomorrow, I'm not at work right now and > am too tired to ssh and etc...
No problem. > Just one point: we've got a quite recent gcc installed on our Solaris, > I'd say gcc 4.2 or even 4.4.2 not quite sure (gcc4.something at > least), and there is a gfortran binary installed with it ,but no > libgfortran.so... That does not make any sense. To the best of my knowledge, if gcc is built with Fortran support, then it will have a library libgfortran.so. However, where that might be on your file system I don't know. Can you send me the output of $ gcc -v $ gfortran -v $ command -v gcc $ cmmand -v gfortran on your system. If you have a recent gcc, then my binary library package should not be necessary. I think what is probaby happening is that the file libgfortran.so in the Sage binary is a link to a non-existant file on your file system. In which case it should be deleted. BTW, what SPARC system do you have? If you have something like an M3000 or better, then building the latest Sage from source should not take too long. If its a Blade 100/2000/2500 or any of the "CoolThreads" machines, than building Sage will take a very long time. The CoolThreads (T1, T2 and T2+ CPUs) are not well suited to running Sage, though they will run it. http://t2nb.math.washington.edu:8000/ is running in a zone on a Sun T5240. It is quite slow, as those CPUs are ill suited for this sort of task. > So i guess we have a recent enough gcc, but not the gfortran lib for > dynamic linked binaries or something like that (no idea about Solaris > package managment). The only packages I'm aware of for a recent gcc will be from Blastwave. In which case, I think the library might be in /opt/csw/gcc4/lib/libgfortran.so If that is your recent gcc, then I would suggest adding /opt/csw/gcc4/lib/ to your LD_LIBRARY_PATH $ LD_LIBRARY_PATH=/opt/csw/gcc4/lib/:$LD_LIBRARY_PATH $ export LD_LIBRARY_PATH Be aware. if Sage finds a recent gfortran, but the C or C++ libraries are old, then Sage will run, but it will not run perfectly. One of the self-tests will fail. Sage must link to recent versions of all the libraries, and not old ones. > Of course I might be wrong. I'll be running more test tomorrow > afternoon. > > Cheers, No problem. I will be out part of tommorow, but I'll try to respond as quickly as possible. PS, when you first run Sage, you will need to have /opt/ccs/bin in your path, so Sage can find 'm4', which it needs whenever a build of Sage is moved. Dave -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
