Accessing the compiler from another host using NFS

[Glenn_Persson]

Hi
Is it possible to access and run the ifort compiler from another host using NFS?
The problem I guess will be the absolute paths in the setup script.

[Ron_Green]

Quoting - Glenn Persson

Hi
Is it possible to access and run the ifort compiler from another host using NFS?
The problem I guess will be the absolute paths in the setup script.

NFS is the only way I install my compilers. Not a problem. Go into the Custom installation and simply give it another installation target that is on the NFS. The ifortvars.sh/csh file will contain that path. Do the install on a typical client server, as the actual exported path on the NFS server is probably different than the mount point (perhaps not).

Do NOT try to copy an installation from one dir to another, since as you mentioned there are a number of scripts that put the original install path into them.

Then setup the INTEL_LICENSE_FILE env var in the default user environment and point it to the location of the license file in the NFS dir (yes, make sure the license file is also exported). So you may put a special license dir on the NFS also, lets say you have /nfsdir/intel/Compiler as your mount point. Setup a /nfsdir/intel/Compiler/licenses directory, drop the licenses in this shared FS and set INTEL_LICENSE_FILE to this directory in a system-wide startup file like /etc/profile

ron

[Ron_Green]

One other little trick I do: I do like to add the 'source ..../ifortvars.sh' in /etc/profile. But as you know, the versions are a problem since they change all the time.

using the nfs strategy I just showed, I set up a 'latest' symbolic link like this for example

ln -s /nfsdir/intel/Compiler/11.0/083 /nfsdir/intel/Compiler/latest

then I can set up /etc/profile:

source /nfsdir/intel/Compiler/latest/bin/ifortvars.sh intel64

Then when I add new versions I simply have to update the 'latest' sym link and not have to worry about /etc/profile.

cheers

ron