HP 9000 Cross Development Environment for HP Integrity Systems Release Notes

HP-UX 11i v2 and HP-UX 11i v3

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

The information contained in this document is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

UNIX is a registered trademark of The Open Group.

January 2009


This document discusses the most recent product information on HP 9000 Cross Development Environment for Integrity (HP XPADE).

This document discusses the following topics:

1 Announcement

This is the first release of HP 9000 Cross Development Environment for Integrity systems (HP XPADE). The first release version of HP XPADE is B.11.23.01 for HP-UX 11i v2 and B.11.31.01 for HP-UX 11i v3.

This solution enables compiling and linking of HP 9000 code on HP-UX 11i for HP Integrity servers. This solution facilitates reduced usage of HP 9000 systems and uses Integrity Systems to build HP 9000 Applications. It also enables deployment of more HP 9000 C/C++ applications on Integrity systems running under Aries which require compilation and/or linking as part of installation or bring up or runtime or operation. Thus enabling HP 9000 server consolidations and migration onto HP Integrity server.

2 HP XPADE

This section describes new features introduced in this release of HP XPADE.

This section addresses the following topics:

2.1 Introduction

HP XPADE is targeted for HP 9000 HP-UX C/C++ applications that require compilation and/or linking as part of installation procedure, bring-up or runtime. It also provides a complete and simplified development environment for HP 9000 on Integrity platform. Lack of a self contained fully functional HP 9000 applications HP-UX development environment on HP-UX 11i for HP Integrity servers is a bottleneck for migration of certain HP 9000 HP-UX applications.

2.2 Features and Benefits

HP XPADE provides following benefits:

  • A higher value of insurance for investments made on HP 9000.

  • Cost or power savings : Due to reduced usage of HP 9000 systems.

  • HP 9000 applications which require compilation and/or linking as part of installation, bring up or runtime can now be migrated to HP Integrity servers using ARIES.

  • You need not copy header files, libraries, utilities from HP 9000 servers to HP Integrity servers for cross compilation and linking.

  • Easy to install, setup and use through the self contained single installable depot.

  • HP XPADE solution is fully tested and supported by HP.

  • Similar high quality and testing as current releases on HP 9000 HP-UX servers.

  • HP XPADE can co-exist with Integrity native C/aC++ Developers Bundle on same Integrity server.

2.3 HP XPADE content

The HP XPADE version contains:

  • HP 9000 Cross compilation environment

  • Development Environments available for HP-UX 11i v2 and HP-UX 11i v3 for C/C++ applications

  • HP 9000 compilers, tools, header files, libraries

    • Files from /usr/include, /usr/lib,/usr/lib/pa20_64 directories

  • Generated Objects get a Signature to be able to identify them as being compiled in this environment.

    • what or odump –comp command on target object displays compiler version starting with letter “X” instead of “B” as shown in the HP 9000 native bundles. This indicates use of compilers bundled with XPADE.

      For example:

      Odump – comp command displays: X111118 (for ANSI C) and X.03.80 (for C++ compiler compiled objects).

      What command displays: X.11.11.18 (for ANSI C) and X.03.80 (for C++ compiler compiled objects).

  • HP 9000 Objects built in this environment can be run only in the same environment on Integrity through ARIES.

  • Deploying the compiled binaries and libraries back on HP 9000 server is not supported.

For more details, see the Product overview section in the website:

www.hp.com/go/xpade

3 Installing and Using HP XPADE

This section addresses the following topics:

3.1 What Is Available as Part of HP XPADE Depot

The HP XPADE depot contains the following:

  • All files part of AR0709 C/aC++ Developer's Bundle - excluding HP Code Advisor and Sentinel products

    • HP 9000 C/aC++ compiler, linker, and linker tools.

    • HP 9000 linker and linker tools are already available on HP-UX 11i for HP Integrity

  • System header files and shared libraries (required files from /usr/include, /usr/lib and /usr/lib/pa20_64 directories) from:

    • HP-UX 11i v2 0712 OEUR for HP 9000 servers (for 11i v2 XPADE)

    • HP-UX 11i v3 0709 OEUR for HP 9000 servers (for 11i v3 XPADE)

    • milli.a (32-bit and 64-bit).

  • XMotif libraries and header files

3.2 What Is Not Included as Part of HP XPADE Depot

The HP XPADE depot does not include the following:

  • Archive libraries from /usr/lib and /usr/lib/pa20_64 directories, except milli.a (32-bit and 64-bit) - use shared libraries instead of archive libraries.

  • Non HP-UX base OE elements

    • ISU components - header files, libraries

    • HP 9000 F90 compiler - HP XPADE is meant for C/C++ applications only.

    • HP 9000 HP-UX lex, yacc tools and corresponding libraries - use native utilities.

  • Manual pages for the system header files and libraries.

  • Transition link (tlinks) database.

  • All non library files and directories under /usr/lib and /usr/lib/pa20_64 on HP 9000 HP-UX 11i v2/v3.

  • HP 9000 HP-UX make command - use native make utility.

  • Tools and utilities from /bin and /usr/bin directories on HP 9000 HP-UX 11i v2/v3.

  • Symbolic links that point to

    • Original files outside XPADE installation root

    • Original files not present on the server

  • Following subdirectories on HP 9000 HP-UX 11i v2/v3

    • /usr/lib/libp

    • /usr/lib/pa2.0

    • /usr/lib/pa1.1

    • /usr/lib/nls

    • /usr/lib/libp

3.3 Limitations

HP XPADE solution has the following limitations/exceptions:

  • XPADE is not a general replacement for PA-RISC development environment.

  • Deployment of XPADE generated objects (*) on HP 9000 servers is not supported. XPADE generated code (*) must be used on HP Integrity server under ARIES.

  • Build time under XPADE may increase by up to 2x compared to HP 9000 servers for large builds.

  • Make files may require modifications.

  • No cross development between HP-UX 11i v2 and v3.

  • No man pages for HP 9000 header files and libraries.

  • No support for transition links - tlinks database not included.

  • No support for development environments prior to HP-UX 11i v2 (11.23)

    • No support for building HP-UX 10.x, 11.00 and 11.11 object files, libraries and executables.

  • No support for -G/-p options.

  • No support for PBO (profile based optimization) builds.

  • No support for tools which have already been deprecated on HP 9000 servers.

  • No support for mixing of HP 9000 and HP Integrity object code.

  • No support for static linking of libraries and executables if the target depends on archive versions of system libraries from /usr/lib or /usr/lib/pa20_64.

3.4 Installing and Setting up HP XPADE Depot

To install HP XPADE depot, complete the following steps:

  1. Install the downloaded HP XPADE depot file using the following command:

    root# swinstall –s < absolute path of the xpade depot >

  2. Set environmental variables to refer to XPADE environment:

    On HP–UX 11i V3 system:

    export SDKROOT=/opt/XPADE/v3 
    export TARGETROOT=/opt/XPADE/v3
    

    On HP–UX 11i V2 system:

    export SDKROOT=/opt/XPADE/v2
    export TARGETROOT=/opt/XPADE/v2
    

HP XPADE is now installed and ready for usage.

3.5 HP XPADE Recommendations

Following are some of the recommendations for using HP XPADE:

  • Install the latest Aries patch for HP-UX 11i v3. To download the latest Aries patch, see http://www.hp.com/go/aries.

  • For using HP XPADE on HP-UX 11i v3, ensure that the kernel tunable parameter base_pagesize is set to it's default value (4 KB) by using the following command:

    $/usr/sbin/kctune base_pagesize

    Table 1 base_pagesize default values

    Tunable Value Expression
    base_pagesize 4 Default
  • The Debugger tool is not packaged along with HP XPADE as it is already getting delivered on Integrity systems. To use the debugger tool, Integrity debugger needs to be installed on your system in the default location. If you do not have the Integrity debugger, download the latest Integrity debugger from the DSPP debugger external page http://www.hp.com/go/wdb and install it in the default directory. And also install the HP 9000 debugger latest patch.

3.6 Using HP XPADE

To use HP XPADE to build or test PA-RISC applications on Integrity, follow the steps mentioned below as relevant:

  1. Copy your HP 9000 application source files to the target Integrity system where HP XPADE is installed.

  2. Change the$PATH variable to pick up compiler from HP XPADE directory.

  3. Update makefile to pick up libraries and headers from HP XPADE directory.

  4. Change makefile to use shared libraries instead of archive libraries if any archive library is used in your product build scripts. This is because, the PA archive libraries are not part of HP XPADE package as these are not officially supported.

    For example:

    • Update your makefile if it is using /opt/XPADE/v2/usr/lib/libc.2 instead of /CLO/BUILD_ENV/usr/lib/libc.1 .

    • Update makefile if it is using -aarchive or DFLAGS="-Wl,-a,archive”, update it as DFLAGS="-Wl,-a,shared”. Ensure your make file does not contain –aarchive in it.

  5. Copy any 3rd party libraries that you may need to compile your product.

  6. Use native binaries as some standard PA-RISC binaries are not included as a part of HP XPADE.

    For example:

    Use native binaries for binaries, such as make, yacc, lex etc.

  7. Build the HP 9000 application on Integrity. The HP 9000 object will be created. File <Object> command will indicate that the object file generated is a PA-RISC object.

  8. Run the resultant PA binary or use the generated object file as appropriate.

      Note:
    • Resultant binaries are for use on Integrity systems only.

    • And in XPADE environment only for any runtime compilation/build dependencies

  9. Debug the product using the PA-RISC developer environment.

4 Feedback and Support

HP encourages your comments concerning this product. You can direct your queries, share your experience, or suggestions by writing to us at:

For more updates on HP XPADE, visit us at:

http://www.hp.com/go/xpade

Support:

  • HP XPADE is supported through the same support mechanisms and channels as HP C/aC++ Developer's Bundle.

  • Contact the HP support organization at their website, the IT Resource Center (ITRC) with details about your problem.