Installation guide

• To generate a list of functions that your application needs, and to
compile without allowing any library definitions on the command line
when building your ULTRIX application, use the following command:
% cc file_name.c -L
Do not include any additional system -l directory options. The −L
option inhibits ld from searching the standard directories for libraries.
The ld command will issue messages identifying any unresolved
symbols. The following short scripts can help you locate the files
containing objects that the compiler fails to resolve:
– Use the following command line to locate references to a particular
string (what to find in the following example) in all files
contained in the working directory or in subdirectories of the
working directory:
% find . -type f -print | xargs grep "what to find" > logfile
Typically, this command is used from the /usr/include directory
to locate information in header files.
– The following script searches every library archive (*.a) on the
system for the object named as its first command-line argument:
#! /bin/sh
for i in /lib/*.a /usr/lib/*.a; do
ar t $i | grep $1 && echo "$1 found in $i"
done
Use this script (called arfind in this example) as follows:
% arfind object-to-find
See Section 7.6.1 for more information on libraries.
7.3 Migrating to a 64-Bit Environment
The 64-bit DIGITAL UNIX system is different from the 32-bit ULTRIX
system in the size of addresses, the availability of 64-bit integer types, the
data type alignment restrictions, byte and word accessibility, and
interoperability between 32-bit and 64-bit systems. These differences affect
the following areas in your programs:
• Pointers
• Constants
• Structures
• Variables
• Library calls
Migrating Your ULTRIX Application to a DIGITAL UNIX System 7–5