|
|
United States-English | |
|
|
 |
|
HP-UX 11i December 2006 Release Notes: HP Servers and Workstations > Chapter 2 Introduction
to HP-UX 11i Version 1
HP-UX 11i v1 Compatibility |
|
|
HP has a long record of providing HP-UX compatibility. Because it protects your investment and allows you to upgrade easily, compatibility is an important feature that HP has always recognized and that HP customers have come to expect. Compatibility requirements span across HP-UX products to third-party products as well. All third-party products (and those products they call) are equally important components in the complete customer environment. Customer solutions often have complex, multiple chains of dependent applications spanning the entire range of HP-UX products as well as third-party products. One broken link in the chain of dependencies may result in an application that no longer works. Support for the unbroken string of compatibility on HP-UX is one of the biggest and best benefits provided by HP. HP-UX supports forward compatibility from 11.0 to 11i. This section describes what this means for executable applications, object files, source files, data, and libraries. Compatibility exceptions, including exceptions pertaining to Superdome systems, are discussed in Chapter 14, “Compatibility,” in the HP-UX 11i December 2004 Release Notes (and previous editions), available at http://docs.hp.com/en/oshpux11i.html. The following types of compatibility are supported from 11.0 to 11i for well-behaved applications:
(For known exceptions to compatibility from HP-UX 11.0 to 11i, see “Known Compatibility Exceptions from HP-UX 11.0 to 11i” in the HP-UX 11i December 2004 Release Notes [and previous editions].) A well-behaved application adheres to the following characteristics:
An application that has run on HP-UX 11.0 will continue to run with the same behavior on 32-bit and 64-bit HP-UX 11i. This includes executables, binary files that have been processed by the HP link editor with ld or indirectly with the compiler, and can be run by the HP-UX loader (exec). Software that has been compiled on an HP-UX 11.0 release can be recompiled without change on HP-UX 11i. The term source includes input source to compilers, scripts, and makefiles. An 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. For example, applications should access the password file information via getpwent() rather than directly reading the file in order to maintain data compatibility. A relocatable object can be a file (.o), shared library (.sl), or an archive library (.a). Several types of object relocatable compatibility are below (note that some executables are not supported): Release-to-release relocatable object binary compatibility: If an executable is created by linking with forward-compatible, relocatable objects from different releases—or by using shl_load() and dlopen() to dynamically load shared libraries built on a different release—than the application is only supported from HP-UX 11.0 to 11i. However, linking pre-HP-UX 11.0 libraries and HP-UX 11.0 and 11i libraries in one relocatable object/executable is not supported.
Archive and shared relocatable object compatibility: An executable that is created by linking with a shared library that has dependencies on an archive library (a situation that typically occurs when linking with archive system libraries) is not supported. Data model relocatable object compatibility: An executable created by linking with a mixture of 32-bit and 64-bit objects is not supported. The loader will not permit this. Compatibility issues or exceptions have been noted for the following products or features that have been updated in December 2006. For details, see the indicated pages. For documentation of compatibility issues or exceptions in previous updates to HP-UX 11i v1, see the previous editions of the HP-UX 11i Release Notes, available at http://docs.hp.com/en/oshpux11i.html. For information about the support of products not listed in elsewhere in this document, refer to the product’s individual documentation, which may be found at the following locations:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
