SUMMARY: Package building, installing, and

From: Marc S. Gibian (
Date: Fri Oct 04 1996 - 16:14:49 CDT

The answer is that the only language libraries bundled into Solaris 2.5 are c
and c++. Thus, the product is responsible for installing any dynamic libraries
it needs. The licensing of the SPARCworks product includes permission to
redistribute, amoung other things, the dynamic library executables built by the
language product.

I have added a dynamic library area to my customer's product's install area and
added it to the end of the LD_LIBRARY_PATH, or LD_RUN_PATH at build time.
Putting it at the end will facilitate picking up newer versions if they should
be installed earlier in the path.

My thanks to: (Jack Reiner) (Jason Noorman) ( Andy J. Stefancik 237-2164 )
Casper Dik <casper@holland.Sun.COM>

Marc S. Gibian
Telos Consulting Services phone: (617) 377-6350
PRISM/TFS email:

attached mail follows:

I am producing a package based install for my customer's product. A lot of it is
working, but there are a number of critical issues remaining to be resolved. One
of these relates to the dynamic library.

I have noticed that this library is NOT installed in the Solaris 2.5 install and
not present in any of the packages included in the OS media. For development
environment purposes this was not a big deal, we just installed the compilers
anyway, so developers could build the product, and got along the
way. On the delivered software, there is no need for the compilers (since the
end user is not building software).

So, my questions:

1. I presume that this library file must be added to the installation materials
for the product?

2. Is there a "standard" way to do this? I tried looking through the compiler
packages and found that the dynamic libraries are bundled into a single package
with the static libraries AND that package is dependent on a true developer-only
package, so I can't just redistribute an existing package?

3. WHERE should it go? On the development platform, this library is only found
in /opt/SUNWspro/lib, but I can't find how the executable's reference to gets resolved to that location. The only environment variable I can
find that comes close is:


And that seems a development environment item?

4. If I include in the product package, how do I ensure an existing
copy already on the target system(s) does not get replaced or duplicated by my
package's install, unless necessary due to versioning issues?


Marc S. Gibian
Telos Consulting Services phone: (617) 377-6350
PRISM/TFS email:

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:11 CDT