Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a Workgroup
Compatibility Between HP-UX Releases 10.x and 11.x
Chapter 4 449
Source Compatibility
32-bit software that compiled on an HP-UX 10.x release can be
recompiled without change on HP-UX 11.0. The term “source” includes
input source to compilers, scripts and makefiles.
Data Compatibility
A 32-bit application can continue to access persistent data files, such as
system files, backup/recovery formats, and HP-documented data formats
via supported APIs in the same manner as the previous release. A 64-bit
application can access the same data in the same manner as a 32-bit
application. For example, if you access the password file information via
getpwent() rather than directly reading the file, your application will
maintain data compatibility.
Upgrade Compatibility
Customized configurations and data from HP-UX 10.x are preserved
upon upgrade to 32-bit or 64-bit HP-UX 11.0.
Relocatable Binary Compatibility
A relocatable object can be an .o file, shared library .sl, or an archive
library .a.
• Release-to-release relocatable object binary compatibility.
Release-to-release relocatable object binary compatibility is not
supported. In other words, if you link an application with
forward-compatible, relocatable objects from different releases or use
shl_load() or dlopen() to dynamically load shared libraries built
on a different release from the application, the resulting executable
is not supported.
This can occur, for example, when you recompile your components on
HP-UX 11.0, but link with ISV libraries that were created for HP-UX
10.x. As a result, if one object is recompiled on 11.0, all objects that
comprise the executable must be recompiled on 11.0; you cannot link
both pre-11.0 libraries and 11.0 libraries in one relocatable
object/executable. Note that you will not see any warning messages if
you do this; but the executable may exhibit incorrect behavior.
• Archive and shared relocatable object compatibility.