R build needs a real FORTRAN in the PATH

[yaseppochi (Stephen J. Turnbull)]

The R configure script will eventually try to find a FORTRAN compiler named `fc' if no other FORTRAN compiler is available. However, on my Mac OS X 10.4.10 "Tiger" system, there is a script /usr/bin/fc which apparently just invokes the Bourne shell builtin of that name. The configuration fails with

checking how to get verbose linking output from fc... configure: WARNING: compilation failed

checking for Fortran 77 libraries of fc... 
checking how to get verbose linking output from gcc -std=gnu99... -v
checking for C libraries of gcc -std=gnu99...  -L/opt/local/lib -L/usr/lib/gcc/powerpc-apple-darwin8/4.0.1 -L/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../.. -lSystemStubs -lSystem
checking for dummy main to link with Fortran 77 libraries... none
checking for Fortran 77 name-mangling scheme... configure: error: cannot compile a simple Fortran program
See `config.log' for more details.

I'm not sure what the right solution for MacPorts is, but for me installing the g95 port allowed R to build.

[jmroot (Joshua Root)]

CC maintainer.

[blb@…]

R currently has gcc42 and gcc43 variants, with gcc43 being the default; these install a fortran compiler, so that should solve this issue. Speak up if that's not the case.

[(none)]

Milestone Port Bugs deleted