different versions of libCrun.so

I am using Studio 11.

my executable just would not run with an older version of /usr/lib/sparcv9/libCrun.so on a machine and later I find out that a different libCrun.so is available with the Studio installation. Using LD_LIBRARY_PATH to pick up the Studio copy, everything just works.

I believe the best solution is patching the system. I am wondering if packaging the Studio copy of libCrun.so (and whatever it uses) is acceptable. I know that the system copy may be newer than the one coming with the compiler and changing the loader setup for my process will affect all the subprocesses. Is there a way to figure which one is newer?

Thanks.

[669 byte] By [algonaut] at [2007-11-26 9:06:19]
# 1
Figuring out which one is newer is easy:[code]$ version /usr/lib/libCrun.so.1version of "/usr/lib/libCrun.so.1": Sun C++ 5.7 s10_74 2004/12/11$ which version/opt/SUNWspro/bin/version[/code]
MaximKartashev at 2007-7-6 23:19:27 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 2

The only acceptable solution is patching the client system with the required C++ RUntime LIbray patch.

The library is part of a package that includes multiple libraries and other files that work together. Replaceing just one library can result in version skew that will cause some programs to fail.

Copying libraries into /usr/lib on a client system is also not a viable solution. It defeats the package discipline that assures that the system knows what is installed and what patches can be backed out.

Get the appropriate C++ Runtime LIbrary patchers here

http://developers.sun.com/prodtech/cc/downloads/patches/index.jsp

and install the patches on all client systems. You can alway install a newer patch than what is required.

clamage45 at 2007-7-6 23:19:27 > top of Java-index,Development Tools,Solaris and Linux Development Tools...