Patch-ID# 100807-04
Keywords: sparcworks manager dynamic linking asian openwindows Mars
Synopsis: Sparcworks 2.0.1: statically linking X11 library doesn't run on Asian OW
Date: Jul/07/94
Solaris Release: 2.2, 2.3, 2.4
SunOS release: 5.2, 5.3, 5.4
Unbundled Product: Sparcworks
Unbundled Release: 2.0.1
Topic: relink sparcworks manager dynamically against X11 instead of statically
BugId's fixed with this patch: 1109118 1109394 1143654 101428 1169127
Changes incorporated in this version: 1169127
Relevant Architectures ('arch -k' values if kernel specific): sun4
Other patches which conflict with this patch:
This patch obsoleted by:
Files included with this patch: sparcworks
Problem Description:
(rev 01)
1109118 sparcworks is linking X11 library statically
1109394 The sparcworks manager does not work with the 493 OS
(rev 02)
Removed OpenWindows package name from dependency list
(rev 03)
Fixed problem with pkginfo giving wrong patchid
(rev 04)
1169127: Patch 100807-03 would not install
[ 11/17/92 ]
% cd /net/kimiko/export/mars/mounts/sunpro/2.0.1/SUNWspro/swmgr/bin
% ldd sparcworks
libtt.so.1 => /usr/openwin/lib/libtt.so.1
libxview.so.3 => /usr/openwin/lib/libxview.so.3
libolgx.so.3 => /usr/openwin/lib/libolgx.so.3
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libintl.so.1 => /usr/lib/libintl.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libc.so.1 => /usr/lib/libc.so.1
libw.so.1 => /usr/lib/libw.so.1
It is linking XView dynamically but linking X11 statically.
It causes a serious problem on Asian OpenWindows.
It doesn't run on it.
----------------------------------------------------------------------------
Type "sparcworks" with the 4/93 OS. You will get the following:
ld.so.1: sparcworks: relocation error: symbol not found: XwcDrawString: referenced in /usr/openwin/lib/libxview.so.3
Killed
XwcDrawString was introduced in libxview in the 493 build, but libX11 defines
it. sparcworks does not dynamically link with libX11, so I suspect that it
may statically link in the mars version of libX11 that does not define XwcDrawString.
Patch Installation Instructions:
--------------------------------
Generic 'installpatch' and 'backoutpatch' scripts are provided
within each patch package with instructions added in this section.
Other specific or unique installation instructions may also be
necessary and should be described below.
Special Install Instructions:
-----------------------------
None.
Instructions to install patch using "installpatch"
--------------------------------------------------
1. Become super-user.
2. Apply the patch by typing:
//installpatch /
where is the directory containing the patch and
is the patch number. must be a full path name.
Example:
# /tmp/123456-01/installpatch /tmp/123456-01
3. If any errors are reported, see "Patch Installation Errors" in
the Command Descriptions section below.
Rebooting the system or restarting the application after a successful
patch installation is usually necessary to utilize patch.
NOTE: On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT.
Instructions for backing out patch using "backoutpatch"
-------------------------------------------------------
1. Become super-user.
2. Change directory to /var/sadm/patch:
cd /var/sadm/patch
3. Backout patch by typing:
/backoutpatch
where is the patch number.
Example:
# 123456-01/backoutpatch 123456-01
4. If any errors are reported, see "Patch Backout Errors" in
the Command Descriptions section below.
Instructions for identifying patches installed on system:
----------------------------------------------------------
Type:
grep SUNW_PATCHID /var/sadm/pkg/*/pkginfo |cut -d: -f2 |sort -u
Command Descriptions
--------------------
NAME
installpatch - apply patch package to Solaris 2.x system
backoutpatch - remove patch package from Solaris 2.x system
SYNOPSIS
installpatch [-u] [-d]
backoutpatch
DESCRIPTION
These installation and backout utilities apply only to
Solaris 2.x associated patches. They do not apply to Solaris
1.x associated patches. These utilities are currently only
provided with each patch package and are not included with
the standard Solaris 2.x release software.
OPTIONS
installpatch
-u unconditional install, do not verify file attributes
-d do not save original files being replaced
DIAGNOSTICS
Patch Installation Errors:
--------------------------
Error message: Patch has already been applied.
Explanation and recommended action: This patch has already been
applied to the system. If the patch has to be reapplied
for some reason, backout the patch and then reapply it.
Error message: The following validation errors were found:
Explanation and recommended action: Before applying the patch,
the patch application script verifies that the current
versions of the files to be patched have the expected
fcs checksums and attributes. If a file to be patched has
been modified by the user, the user is notified of this
fact. The user then has the opportunity to save the
file and make a similar change to the patched version.
For example, if the user has modified /etc/inet/inetd.conf
and /etc/inet/inetd.conf is to be replaced by the patch,
the user can save the locally modified /etc/inet/inetd.conf
file and make the same modification to the new file
after the patch is applied. After the user has noted all
validation errors and taken the appropriate action for
each one, the user should re-run installpatch using
the "-u" (for "unconditional") option. This time, the
patch installation will ignore validation errors and
install the patch anyway.
Error message: Insufficient space in /var/sadm to save old files.
Explanation and recommended action: There is insufficient
space in the /var/sadm directory to save old files.
The user has two options for handling this problem:
(1) generate additional disk space by deleting unneeded
files, or (2) override the saving of the old files by
using the "-d" (do not save) option when running installpatch.
However if the user elects not to save the old versions of
the files to be patched, backoutpatch CANNOT be used.
Error message: Save of old files failed.
Explanation and recommended action: Before applying the patch,
the patch installation script uses cpio to save the old
versions of the files to be patched. This error message
means that the cpio failed. The output of the cpio
would have been preceded this message. The user should
take the appropriate action to correct the cpio failure.
A common reason for failure will be insufficient disk
space to save the old versions of the files. The user
has two options for handling insufficient disk space:
(1) generate additional disk space by deleting unneeded
files, or (2) override the saving of the old files by
using the "-d" option when running installpatch. However
if the user elects not to save the old versions of the
files to be patched, the patch CANNOT be backed out.
Error message: Pkgadd of package failed. See
/tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Error message: error while adding patch to root template
Explanation and recommended action: The install script
determined this system to be a client server. The attempt
to apply the patch package to the appropriate root
template space located under /export/root/templates
failed unexpectedly. Check the log file for any failure
messages. Correct the problem and re-apply the patch.
Patch Backout Errors:
---------------------
Error message: Patch has not been applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message: Patch was installed without backing up the
original files. It cannot be backed out.
Explanation and recommended action: The -d option of installpatch
was set when the patch was applied. As a result, the original
files were not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message: Pkgrm of package failed. See
/var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file
for the reason for failure. Correct the problem and
run the backout script again.
Error message: Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT.
After a patch package has been installed pkginfo(1) will
not recognize the SUNW_PATCHID macro in the patch package
pkginfo file. Instead, to identify patches installed on
the system use the grep command method described in the
patch README.
SEE ALSO
pkgadd(1), pkgchk(1), pkgrm(1), pkginfo(1)