Kbase 21455: How To Have A Clean Shared Library Path From Progress Session
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/04/2002 |
|
Status: Unverified
GOAL:
How To Have A Clean Shared Library Path From Progress Session.
FACT(s) (Environment):
Progress 9.x
FIX:
Launch the Progress session directly with _progres, or unset the shared library path after shelling out to UNIX.
When shelling out to UNIX from a Progress session, the shared library path environment variable is pre-set even though it wasn't set prior to starting the Progress session. This causes problems when attempting to compile C programs from the shell. On some Unix platforms the C compiler looks in the default directory (/usr/lib ) for the shared C library when the shared library path is not set. If the shared library path is set, the compiler will look in the set directory.
Both pro or mpro scripts call slib_env to set various shared library paths to $DLC/lib. From there, pro and mpro launch the _progres executable. When shelling out to UNIX from a Progress session, Progress doesn't alter the environment settings. Instead, it inherits all the prior settings to start _progres. Thus all the shared library path will be set to $DLC/lib by slib_env.