HP-UX 11i Version 1.5 Release Notes, May 2001
Table Of Contents
- 1 Overview of the Release Notes
- 2 Workstation/Server Specific Information
- 3 HP-UX Features
- 4 File and Disk Management
- 5 Networking
- 6 Commands and System Calls
- 7 Programming
- aC++ Libraries
- Changes to libc
- libcres.a Library
- New libdcekt.sl and libdcecpkt.sl Libraries
- New Linux Compatible API Library
- New locale Libraries
- New Unwind Library
- X11 Libraries
- SNMP
- Machine Dependent Headers
- Threadsafe Documentation
- Obsolescence and Deprecation of APIs
- Linker Toolset
- gprof Multiple Shared Library Profiling
- CXperf Performance Monitoring Support
- HP Caliper
- WDB Debugger Tool
- ADB Debugger Tool
- Fortran
- Packaging for Specific Releases
- 8 Other Functionality
Other Functionality
HP-UX Software Transition Kit (STK)
Chapter 8 151
HP-UX Software Transition Kit (STK)
The HP-UX Software Transition Kit (STK) includes tools and
documentation to help you successfully transition to the Itanium
architecture of HP-UX 11i Version 1.5. To transition your software and
scripts, you may have to resolve issues such as data model and API
changes. Many tools are available to help you resolve these issues. API
file scanners are provided in the HP-UX 11.x STK, while other tools are
part of the HP-UX operating system, are included in HP-UX language
products, or are supplied by third parties.
The HP-UX 11i Version 1.5 (B.11.20) STK provides step-by-step
instructions for performing transitions, a completeset of background and
technical documents, and file scanners to help you identify and resolve
any required API changes in your source files.
In these types of source files:
• C and C++ programs
• Fortran programs
• COBOL programs
• scripts
• Makefiles
The HP-UX 11i Version 1.5 (B.11.20) STK file scanners can help you
locate and fix any changed or obsolete:
• functions
• commands
• path names
• macros
• structures and structure members
• header files
• language keywords
• libraries
• variables
One of the HP-UX 11i Version 1.5 (B.11.20) STK file scanners,
scansummary, helps you plan your transition by summarizing the
number and type of API impacts in your source files. The other tool,
scandetail, helps you resolve those impacts by identifying the file name
and line number in your source where each impact occurs. Both tools
provide links to more detailed information about each impact. The file