<Problems using system versions of open source libs rather than externally provided ones...>
One of the interesting features that no one uses to solve these problems is a per-application ld.config file. Ld allows a -c name option (you need to pass this via LD_OPTIONS since the compilers use -c as well) to specify a per-application ld.config file. This file can be placed relative to the application binary using the $OPTION token. Even better, $OSNAME, $OSREL tokens are available as well, so a single binary could use different library search paths on different releases. Another possible approach is to use symbolic links in /opt/xxx/lib to point to the system version of libraries when available. Another approach is to always use /usr/lib:/usr/sfw/lib:/opt/xxx/lib as the application and library run paths. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts
