critical impact:

ostrip - not available; use strip or mcs (CrUn229)

Problem description

The ostrip development tool exists on Tru64 UNIX, but not on HP-UX. However, you can use strip as a replacement.

You can use the ostrip development tool to minimize or delete debug information in an object file, executable, or shared library.

Identifiers

ostrip

Old behavior

% ostrip -x a.out

See also

• Background information on compilers and development environment impacts
• Background information on Tru64 UNIX migration environment impacts
• ostrip(1)

Solution description

Use strip to achieve similar results in the HP-UX environment.

Some of the features of ostrip are available on HP-UX by calling strip or mcs (available on a temporary basis in the Tru64 UNIX Migration Environment for HP-UX). The following table gives the equivalent HP-UX command, if any, for each ostrip option:

Tru64 UNIX command             HP-UX command
------------------             ----------------
ostrip -c object               mcs -d object
ostrip -g object               No mapping
ostrip -j file object          No mapping
ostrip -m object               No mapping
ostrip -r object               No mapping
ostrip -R object               No mapping
ostrip -s object               strip -s object
ostrip -t file object          No mapping
ostrip -x file                 strip -l object
ostrip -z object               No mapping
ostrip -Z object               No mapping

See mcs(1) in the Migration Environment for more information. The Migration Environment contains Tru64 UNIX APIs, development tools, and commands and utilities to assist customers in migrating their applications from Tru64 UNIX to HP-UX.

New behavior

% strip -l a.out

See also

• strip(1)
• Tru64 UNIX Migration Environment User's Guide

Problem summary