Solaris Studio compilations on cluster builds are unable to find generated header files.
This behavior is a side effect of the way the Solaris Studio compiler searches for header files. Other compilers, such as
gcc, attempt to open each header file in each specified include directory, allowing ElectricAccelerator to record that the attempt occurred. With this metadata, ElectricAccelerator is then able to detect job conflicts and re-run jobs appropriately. However, with Solaris Studio, the compiler instead obtains directory listings, which works counter to an optimization added in ElectricAccelerator v6.0 where directory modifications no longer trigger conflicts.
To work around this issue, you can specify the option
--emake-readdir-conflicts=1. It is advisable that you not run with the option on all the time, but that depends on how often header files are added/moved/deleted in your environment. Additional details are available in Knowledge Base article KBEA-00104
- Product versions: 6.0 and later
- OS versions: Solaris