Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
Open System Services Porting Guide—520573-006
9-1
9
Porting From Specific UNIX Systems
This subsection discusses other vendors’ UNIX environments for developing or
compiling C and C++ programs that you want to port to the OSS environment. The
following topics are discussed:
•
The UNIX Workstation Development Environment on page 9-1
•
C Compilation on a Workstation on page 9-7
•
Resolving the Endian Problem on page 9-8
The UNIX Workstation Development
Environment
Your UNIX workstation environment should be XPG4 compliant. Your vendor should
specify whether they are compliant in their documentation. XPG4 is a superset of
POSIX.1 and POSIX.2. If a vendor’s product has gone through the XPG4 certification,
they will be branded as being XPG4 certified.
The workstation software discussed in the following subsections can affect what and
how you port applications:
•
Shells on page 9-1
•
Editors on page 9-2
•
Development Tools on page 9-2
Shells
One or more of three shells are available on most UNIX workstations. They are:
•
The Bourne shell, which was developed by Bell Labs.
•
The C shell, which was developed by University of California, Berkeley.
•
The Korn shell, which was also developed by Bell Labs. The Korn shell was
designed to be a superset of both the C shell and the Bourne shell.
The POSIX.2 standard is based upon the Korn shell. Because the OSS shell
implements the POSIX.2 standard, porting scripts from a Korn shell to the OSS shell is
relatively easy. Applications that depend upon shell scripts or shell commands should
be carefully checked to ensure that Open System Services supports all of the
commands and command flags used within the scripts.