Our preference is F77 compilers over F9x ones, as the lists Simon showed reflects - we decided to prefer F95 to F90 in future, though.
My experience is that g77 from gcc-3.4.x is preferable to gfortran. As I said earlier, once gcc-4.0.1 is released (and so R builds with a released version of gcc-4.x.y - 4.0.0 needs worarounds) I will take a another look. So far, using gcc-3.4.4 is both faster and more accurate that gcc-4.0.0. There are a few instances in which loess gives rather different results with gfortran, but they are only visible by diffing postscript files. I will look into converting blas.f to F77 (but not for this release). On Tue, 14 Jun 2005, Marc Schwartz wrote: > On Tue, 2005-06-14 at 22:42 -0400, Simon Urbanek wrote: >> On Jun 14, 2005, at 6:16 PM, Marc Schwartz wrote: >> >>> Interesting. Did you do anything different on the ./configure line? >>> >>> $ ls -l /usr/bin/f95 >>> lrwxrwxrwx 1 root root 8 Jun 13 21:18 /usr/bin/f95 -> gfortran >>> >>> I just tried it again (having installed some FC updates) and I >>> still get g77... >> >> g77 is probed before f95, so if you have both, g77 is picked unless >> you set F77 explicitly. The exact probe sequence is: >> >> g77 f77 xlf frt pgf77 fort77 fl32 af77 f90 xlf90 pgf90 epcf90 f95 >> fort xlf95 ifc efc pgf95 lf95 gfortran (R 2.1.1 beta) >> g77 fort77 f77 xlf frt pgf77 cf77 fl32 af77 f95 fort xlf95 ifort ifc >> efc pgf95 lf95 gfortran ftn g95 f90 xlf90 pgf90 pghpf epcf90 fc (R- >> devel) >> >> I guess Peter simply didn't install g77. >> >> Cheers, >> Simon > > Simon, > > Thanks for that. When I installed FC4, I used the option to install > "Everything", which is what I have done with each prior release going > back to RH 8.0. Of course with many things being moved to Extras, > "Everything" is now a shadow of it's former meaning. > > It is noted that "Everything" includes RPMS that are not explicitly > listed in other pre-defined groups for installation. > > In reviewing the Add/Remove Application GUI, gfortran is listed as an > "Extra Package" in the Development Tools Group. > > g77 is not listed in that Group or in the Legacy Development Group, so > it would appear that it is a "silent" part of the "Everything" > installation procedure. > > Removing the offending RPM: > > rpm -e compat-gcc-32-g77-3.2.3-47.fc4 > > I now get: > > C compiler: gcc -g -O2 > C++ compiler: g++ -g -O2 > Fortran compiler: f95 -g -O2 > > > I re-compiled and did note the warning messages that I believe Peter > referred to: > > f95 -g -O2 -c blas.f -o blas.o > In file blas.f:1561 > > GO TO IGO,(120,150,180,210) > 1 > Warning: Obsolete: Assigned GOTO statement at (1) > In file blas.f:1567 > > ASSIGN 120 TO IGO > 1 > Warning: Obsolete: ASSIGN statement at (1) > In file blas.f:1579 > > ASSIGN 150 TO IGO > 1 > Warning: Obsolete: ASSIGN statement at (1) > In file blas.f:1592 > > ASSIGN 180 TO IGO > 1 > Warning: Obsolete: ASSIGN statement at (1) > In file blas.f:1603 > > ASSIGN 210 TO IGO > 1 > Warning: Obsolete: ASSIGN statement at (1) > > > > make check-all passes with no errors, so no change there. > > > Regards, > > Marc > > > -- Brian D. Ripley, [EMAIL PROTECTED] Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595 ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
