libXp.so.6: cannot open shared object file: No such file or directory
how do you know what Linux package to load?
When installing the Linux operating system, there are many "optional packages" (often known as RPMs) that can be installed. Requirements change, so a new software installation can require a file that you have not previously installed.
How can you find out which bundle to install?
The "yum" utility has a "whatprovides" option to answer this question.
yum whatprovides <file>
So in the example above, you should use the command:
# yum whatprovides libXp.so.6
Loaded plugins: refresh-packagekit, rhnplugin
*Note* Red Hat Network repositories are not listed below. You must run this command as root to access RHN repositories.
Some of the files under the WDIR (for example: user.cns) are not compatible with all versions of SDD (EE/BSXE/PADS/IND) Flow software, and in some cases can actually cause applications to crash. For this reason it is advisable to maintain a different WDIR location for each release. Here is a simple technique for doing so:
Create a Configurator.ini file. Place this file in a folder of your choice, although C:\MentorGraphics\win32 is a good and simple to find location (same directory as the Configurator.exe).
See below format, which will create a C:\WDIR\<release> for each release that you configure to. For example, C:\WDIR\7.9.5EE and C:\WDIR\9.5PADS, for EE7.9.5 and PADS9.5, respectively.
All three lines must appear in order for the WDIR to get set correctly. Change the MGLS_LICENSE_FILE to the port@host (or local file path) for your licensing environment.
Create a CFGR_INI environment variable and set it to the full location of the Configurator.ini file.
For example: CFGR_INI = C:\MentorGraphics\win32\Configurator.ini
On Windows you have the option to set an environment variable as a User variable or a System variable. A User variable takes precedence when the variable is set both as a User and System variable. Setting a System variable requires admin rights and will be available to anyone who logs into the system. User variables are only available to the user but are generally fine for desktop applications.
However, some applications either run as a service or have a component that runs as a service. In cases where the service requires a license (e.g.: Capital Manager), it is imperative that MGLS_LICENSE_FILE be set as a System variable so the service (running under the System user account) can obtain a license.
If you get errors when starting an application service, ensure that ALL required variables are set as System variables.