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
Porting From Specific UNIX Systems
Open System Services Porting Guide—520573-006
9-8
GNU C Compiler
Because applications that use strictly ISO/ANSI C semantics are the easiest to
port, your application should compile successfully with the -Xa flag before being
considered ready to port to the OSS environment.
GNU C Compiler
The GNU C compiler supports ISO/ANSI C language syntax and supports a “pedantic”
mode, which requires strict adherence ISO/ANSI C. It supports the following:
•
ISO/ANSI C and Common C.
•
Relevant compiler flags:
Because applications that use strictly ISO/ANSI C semantics are the easiest to
port, your application should compile successfully with the -pedantic flag before
being considered ready to port to the OSS environment.
•
Optional additional GNU utilities:
These additional utilities are not provided in the OSS environment. The proper
functioning of your application should not depend upon these tools after it is ported
to the OSS environment.
Resolving the Endian Problem
The term “endian” refers to the order in which a computer numbers and stores its
bytes. There are two kinds of byte-endian ordering:
•
Big endian, in which the most significant byte of a multiple-byte entity (of a word,
for example) is stored first (at the lowest memory byte address or word boundary,
represented as the leftmost byte)
•
Little endian, in which the least significant byte is stored first (represented as the
rightmost byte)
Systems such as NonStop servers, IBM 360 and later mainframes, the IBM RS 6000,
and Sun Solaris use big-endian byte ordering. Systems based on the Intel x86 platform
(such as Microsoft Windows systems), HP OpenVMS systems, and HP Tru64 UNIX®
on the Alpha architecture use little-endian byte ordering.
-ansi Supports ISO/ANSI C syntax.
-pedantic Supports strict ISO/ANSI C syntax.
-w Inhibits all warning messages.
-Wimplicit Warns you whenever a local variable is unused aside from its
declaration.
gmake Maintains groups of programs.
gdb The GNU debugger program.
gas The GNU assembler program.