Hello Dr. McDonald:
I understand why you want to simplify the installation with a network of workstations; we have quite a diverse network ourselves, and we understand the problem.
I’ll answer the easy questions first:
$ pgf77 -rc /usr/local/site/pgitest/linux86/6.0/bin/localrcFC3 test.f
fails because the driver (pgf77) gets confused about whether localrcFC3 is an argument to the -rc switch (which it is) or whether it is another file on the command line. The workaround is to use an equal sign
$ pgf77 -rc=/usr/local/site/pgitest/linux86/6.0/bin/localrcFC3 test.f
However, this won’t work either, in 6.0 at least, because of another bug in the driver. For reasons too technical (meaning someone goofed) to explain, when a user adds an rc file on the command line, the set of file suffixes gets trashed, so the driver doesn’t recognize .f as a Fortran file anymore. I am really sorry about this. The -rc switch isn’t used very often, in fact almost never, so when a bug like this crept in, it didn’t get detected, for which we have no excuse. The workaround is to change the localrcFC3 to start with the line
…rest of your stuff…
and to compile with
$ pgf77 -initrc=localrcFC3 test.f
If the localrcFC3 is in the same directory as the pgf77 driver, you shouldn’t need to put in the full path.
Now for the longer questions:
Unfortunately, localrc is not the only difference between different installs of the PGI compilers. The install process moves include files and libraries into the include/ and lib/ directories depending on the version of glibc and gcc installed on that system. Your RHEL and FC2 systems probably have the same glibc and gcc versions, so the same include and library files, as well as the same localrc file, will work. Your FC3 system has an upgraded gcc, perhaps a different glibc, so the libraries and includes are different, and the localrc is different as well. For 6.0, we really have no simpler way to install. This answers your question about whether the localrc is only used in the link step; it is also used by the compiler for include files, but since include files are not common in Fortran, it is less important than for C (for instance).
However, as I mentioned at the start, we really understand the desire for a single install point for a network of workstations, even when (or especially when) they have different versions of other software. Also, it would be much easier to manage if the compilers didn’t have to be reinstalled when upgrading gcc or the operating system or the glibc libraries. We are working on this, and the hope is to have this in place for 6.1. You will have to run a script on each system to generate the equivalent of the ‘localrc’ file for that system, that will identify which version of gcc and glibc (and any other information) is appropriate, but the actual installation can be put on one NFS directory. Also, after an upgrade of the system, simply running the same script will update the PGI compiler installation. It would be even better if the compilers could auto-detect the gcc and glibc versions, but this is a somewhat lengthy process that you probably don’t want to happen each time you run the compilers.
I’m sorry I can’t help with all the problems, but I think the next release will solve these problems in a painless way.