When I use the Turns Engine and the log-in shell is a Bourne shell derivative (BASH, KSH), PAR does not run on remote nodes.
Reported error messages include:
"/bin/sh: par: not found"
"XILINX is not an identifier"
"ld.so.1: par: fatal: libParBase.so: open failed: No such file or directory"
When the log-in shell is CSH or a derivative, the ".cshrc" file is read before processing other commands invoked by RSH. This file can set up the environment variables required for PAR to run (PATH,XILINX, LD_LIBRARY_PATH).
The Bourne shell and derivatives do not process their respective start-up files when commands are invoked by RSH. Instead, a Bourne shell script must set up the environment variables on remote nodes. If a PAR_M_SETUPFILE environment variable exists, PAR runs the file to which it points on remote nodes before running the remote instances of PAR.
Example Bourne shell script:
NOTE: In the Bourne shell, you must first create a shell variable, then export it, because the Bourne shell does not accept the single set and export step permitted by BASH and KSH.
For more information, please see (Xilinx Answer 1644): "How do I set up and de-bug Multi-Pass Place and Route/Turns Engine/Networked PAR?"