On 18 November 2010 09:01, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > Hi, > >> Can you send me the output of >> >> $ gcc -v >> $ gfortran -v >> $ command -v gcc >> $ cmmand -v gfortran >> >> on your system. >> > Here it is: > bash-3.00$ gcc -v > Reading specs from /usr/local/packages/gcc3/bin/../lib/gcc/sparc-sun- > solaris2.10/3.4.3/specs > Configured with: /sfw10/builds/build/sfw10-patch/usr/src/cmd/gcc/ > gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/ccs/bin/as -- > without-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable- > languages=c,c++ --enable-shared > Thread model: posix > gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
> bash: command: gfortran: not found Those are totally unsuitable for building Sage > But there are other gcc binaries in /usr/local/gcc4. > Here is the content of /usr/local/gcc4/bin: > c++ jcf-dump > cc sparc-sun-solaris2.10-c++ > cpp sparc-sun-solaris2.10-g++ > g++ sparc-sun-solaris2.10-gcc > gcc sparc-sun-solaris2.10-gcc-4.2.0 > gccbug sparc-sun-solaris2.10-gcc-4.4.2 > gcj sparc-sun-solaris2.10-gcj > gcov sparc-sun-solaris2.10-gcjh > gfortran sparc-sun-solaris2.10-gfortran > > with: > bash-3.00$ ./gcc -v > Using built-in specs. > Target: sparc-sun-solaris2.10 > Configured with: ../configure --prefix=/usr/local/packages/gcc4_10 -- > with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable- > languages=c,c++,fortran,objc,java > Thread model: posix > gcc version 4.4.2 (GCC) > bash-3.00$ ./gfortran -v Those are ok, but unless those are in your PATH first, which ~I don't think is the case, then they will not be used when Sage is built. Sage will use the first gcc in your path. Even if you specify a compiler with the CC environment variable, it will probably fail, as many of the packages in Sage have 'gcc' hard-coded and will ignore the CC and CXX environment variables. > Here are some of the computers I have access to: > - SunOS 5.10 Generic_139555-08 sun4v sparc SUNW,T5140 That will run Sage very slowly. The CPUs are ill suited for scientific computing. > - SunOS 5.10 Generic_137137-09 sun4u sparc SUNW,Sun-Blade-1500 That will be quicker for running Sage, despite the fact it is older. >> 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. >> > There is no /opt/css folder. See my correction. It is /usr/ccs/bin/m4 I asume using the GNU version of m4 will work, but it is not somethige that's ever tested on Soliaris. > For m4, I guess the system uses: > bash-3.00$ which m4 > /usr/local/bin/m4 > > I'll try your library now. > > JP Be careful. Note I said that you need to have recent versions of *ALL* the gcc libraries. A failure to have any libgfortran.so will result in a failure of Sage to run at all. A failure to have recent versions of the C and C++ libraries will result in odd behaviour. Some of Sage's self-tests will fail to run properly. I suggest you run from the top level make testlong and wait and see if there are any failures. You might get a few timeout failures on those systems. 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
