Installation guide

/usr/person. To link with that library, use the −l and −L options, as
shown:
% cc -o hello hello.c -L/usr/person -lspecial_math
To link the application that does not use shared libraries, you must specify
the −non_shared option in the cc command line, as shown:
% cc -non_shared -o hello hello.c -L/usr/person -lspecial_math
Although shared libraries are the default for most applications, the
following applications cannot use them:
• Applications that need to run in single-user mode cannot be linked to
shared libraries because the /usr/shlib directory must be mounted to
allow access to the shared libraries.
• Applications whose primary purpose is single-user benchmarks should
not be linked with shared libraries because position-independent code is
less efficient than position-dependent code. Also, there is no benefit to
sharing memory when only one application is running.
• Real-time applications using memory-locking features should not be
linked to shared libraries. Memory-locking functions will lock the entire
shared library into memory.
8.1.2 Symbol Resolution and Shared Libraries
If you link your application with shared libraries instead of archive
libraries, you might notice some differences in the way symbols are
resolved. This section describes these differences.
8.1.2.1 How Libraries Are Searched
The shared libraries supplied with DIGITAL UNIX systems are stored in
the /usr/shlib directory. Place all system shared libraries in this
directory to avoid confusion. When the linker searches for files that have
been specified using the −l option, it searches the following directories, in
order:
• /usr/shlib
• /usr/ccs/lib
• /usr/lib/cmplrs/cc
• /usr/lib
• /usr/local/lib
The linker searches all of the directories for a shared library (an .so file).
If it does not find a shared library with the specified name, the linker
8–2 Postmigration Programming Features