Installation on UNIX/Linux uses install.sh; running this fails with a "runGSkit failure: Return error code: 99" and a "install.sh failure: Return error code: 4".
The full sample output looks like this:
runGSkit failure: Return error code: 99.
runGSkit failure: GSKit check failure, script: /opt/IBM/ITM/ls3263/gs/bin/private_verifyinstall.
runGSkit failure: ls3263 - GSK check error, verifyInstall test failed.
install.sh failure: Return error code: 4.
Diagnosing the problem
Since it failed within runGSkit when it called verifyInstall, review the CH/logs/candle_installation.log file and look for references to runGSkit. For example, output similar to the following might be present:
runGSkit: ----- Running command: /opt/IBM/ITM/ls3263/gs/bin/private_verifyinstall -----
/opt/IBM/ITM/ls3263/gs/bin/gsk7ver: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
Error: Verify Failed
Expected Details of gskit in /opt/IBM/ITM/ls3263/gs
runGSkit: return code from command is 99
runGSkit: ----- End of running command -----
runGSkit: error Return error code: 99
runGSkit: error GSKit check failure, script: /opt/IBM/ITM/ls3263/gs/bin/private_verifyinstall
runGSkit: error ls3263 - GSK check error, verifyInstall test failed
Resolving the problem
In the example above, which is for Linux running on z/OS (zLinux), the libstdc++.so.5 file was not present in the library path. On zLinux, this file comes from the package compat-libstdc++-33-3.2.3-61.s390.rpm. When this package was installed, the problem no longer occurred.
For other platforms, the corresponding architecture-specific package would need to be installed (compat-libstdc++-33-3.2.3-61.x86_64.rpm and compat-libstdc++-33-3.2.3-61.i386.rpm).