Software: | SCO OpenServer Release 5.0.0, 5.0.2, 5.0.4, or 5.0.5* |
RAM: | N/A |
Disk Space: | 20MB |
* This BCM is installed automatically on SCO OpenServer Release 5.0.5 systems.
Perform the following steps as root:
mv C0*.tar /tmp1
cd /tmp1
tar xvf C0*.taruncompress OSRcompat.pkg.Z
pkgadd -d `pwd`/OSRcompat.pkg
The UnixWare 7 versions are installed in an alternate directory tree (/udk).
The BCM installs two types of libraries on SCO OpenServer:
Libraries that go through standard libc interfaces to get system services fall into this category.
An example of the second type of library is libsocket. On SCO OpenServer, sockets are created and manipulated through the socketsys system call. Another example is the UnixWare 7 libc for SCO OpenServer, which maps UnixWare 7 system call numbers to the values expected by the SCO OpenServer kernel, and maps error numbers returned by the SCO OpenServer kernel to the values expected by UnixWare 7 applications. It also maps certain data structures and constants that are different on the two platforms.
Besides shared libraries, certain other files need to be part of the BCM. Such files would be any file that is part of the system and is visible to a running application. This includes, for example, locale files, configuration files, other data files like bitmaps, etc.
Once installed, the SCO OpenServer BCM:
When a binary is run, the new dynamic linker:
NOTE: Some existing SCO OpenServer ELF binaries built with third-party compilers may not run after installing this package on SCO OpenServer. That is because they do not contain the special mark denoting an SCO OpenServer ELF binary.
This mark is created by the SCO OpenServer C compiler, icc, and most versions of gcc that generate SCO OpenServer ELF binaries.
For SCO OpenServer 5.0.4, this problem has been resolved with the Support Level Supplement (SLS) oss472, Binary Misrecognition Patch, available at the SCO ftp site. For earlier releases, follow the procedure described here; the SLS is not required for SCO OpenServer Release 5.0.5.
The mark consists of a special segment of type NOTE.
If an SCO OpenServer binary does not run after installing this package,
you can determine whether it is missing the special mark
by running the dump command:
dump -ov file
You should see an entry denoted as type "NOTE".
If this entry is missing, you may run the command
elfmark(1) to mark the file as an
SCO OpenServer binary:
/udk/usr/ccs/lib/elfmark -t osr5 file
Note that the mark inserted by elfmark is different from the mark created by the standard compilers.
Document version 700b
19 January 1999
© 1999 The Santa Cruz Operation, Inc. All rights reserved.