Linux Standard Base Core Specification for PPC64 2.0.1

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

Portions of the text are copyrighted by the following parties:

The Regents of the University of California
Free Software Foundation
Ian F. Darwin
Paul Vixie
BSDI (now Wind River)
Andrew G Morgan
Jean-loup Gailly and Mark Adler
Massachusetts Institute of Technology

These excerpts are being used in accordance with their respective licenses.

Linux is a trademark of Linus Torvalds.

UNIX a registered trademark of the Open Group in the United States and other countries.

LSB is a trademark of the Free Standards Group in the USA and other countries.

AMD is a trademark of Advanced Micro Devices, Inc.

Intel and Itanium are registered trademarks and Intel386 is a trademarks of Intel Corporation.

OpenGL is a registered trademark of Silicon Graphics, Inc.

Table of Contents
Specification Introduction
ELF Specification
Linux Standard Base Specification
Linux Packaging Specification
Free Documentation License

Specification Introduction

Table of Contents

Foreword

Introduction

I. Introductory Elements

1. Scope

General
Module Specific Scope

2. Normative References

3. Requirements

Relevant Libraries
LSB Implementation Conformance
LSB Application Conformance

4. Definitions

5. Terminology

6. Documentation Conventions

List of Tables
2-1. Normative References
3-1. Standard Library Names

Foreword

This is version 2.0.1 of the Linux Standard Base Core Specification for PPC64. An implementation of this version of the specification may not claim to be an implementation of the Linux Standard Base unless it has successfully completed the compliance process as defined by the Free Standards Group.

Introduction

The LSB defines a binary interface for application programs that are compiled and packaged for LSB-conforming implementations on many different hardware architectures. Since a binary specification shall include information specific to the computer processor architecture for which it is intended, it is not possible for a single document to specify the interface for all possible LSB-conforming implementations. Therefore, the LSB is a family of specifications, rather than a single one.

This document should be used in conjunction with the documents it references. This document enumerates the system components it includes, but descriptions of those components may be included entirely or partly in this document, partly in other documents, or entirely in other reference documents. For example, the section that describes system service routines includes a list of the system routines supported in this interface, formal declarations of the data structures they use that are visible to applications, and a pointer to the underlying referenced specification for information about the syntax and semantics of each call. Only those routines not described in standards referenced by this document, or extensions to those standards, are described in the detail. Information referenced in this way is as much a part of this document as is the information explicitly included here.

I. Introductory Elements

Table of Contents
1. Scope
2. Normative References
3. Requirements
4. Definitions
5. Terminology
6. Documentation Conventions

Chapter 1. Scope

General

The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB.

These specifications are composed of two basic parts: A common specification ("LSB-generic") describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific specification ("LSB-arch") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the architecture-specific supplement for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture.

The LSB-generic document shall be used in conjunction with an architecture-specific supplement. Whenever a section of the LSB-generic specification shall be supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture supplement. Architecture supplements may also contain additional information that is not referenced in the LSB-generic document.

The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation shall provide all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed.

The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification.

Module Specific Scope

This is the PPC64 architecture specific Core module of the Linux Standards Base (LSB). This module supplements the generic LSB Core module with those interfaces that differ between architectures.

Interfaces described in this module are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Chapter 2. Normative References

The specifications listed below are referenced in whole or in part by the Linux Standard Base. In this specification, where only a particular section of one of these references is identified, then the normative reference is to that section alone, and the rest of the referenced document is informative.

Table 2-1. Normative References

Name	Title	URL
64-bit PowerPC ELF ABI Supplement	64-bit PowerPC ELF ABI Supplement, Version 1.7	http://www.linuxbase.org/spec/ELF/ppc64/
DWARF Debugging Information Format	DWARF Debugging Information Format, Revision 2.0.0 (July 27, 1993)	http://www.eagercon.com/dwarf/dwarf-2.0.0.pdf
Filesystem Hierarchy Standard	Filesystem Hierarchy Standard (FHS) 2.3	http://www.pathname.com/fhs/
IEEE Std 754-1985	IEEE Standard 754 for Binary Floating-Point Arithmetic	http://www.ieee.org/
ISO C (1999)	ISO/IEC 9899: 1999, Programming Languages --C
ISO POSIX (2003)	ISO/IEC 9945-1:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 1: Base Definitions ISO/IEC 9945-2:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 2: System Interfaces ISO/IEC 9945-3:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 3: Shell and Utilities ISO/IEC 9945-4:2003 Information technology -- Portable Operating System Interface (POSIX) -- Part 4: Rationale	http://www.unix.org/version3/
Large File Support	Large File Support	http://www.UNIX-systems.org/version2/whatsnew/lfs20mar.html
Li18nux Globalization Specification	LI18NUX 2000 Globalization Specification, Version 1.0 with Amendment 4	http://www.li18nux.org/docs/html/LI18NUX-2000-amd4.htm
Linux Allocated Device Registry	LINUX ALLOCATED DEVICES	http://www.lanana.org/docs/device-list/devices.txt
PAM	Open Software Foundation, Request For Comments: 86.0 , October 1995, V. Samar & R.Schemers (SunSoft)	http://www.opengroup.org/tech/rfc/mirror-rfc/rfc86.0.txt
RFC 1321: The MD5 Message-Digest Algorithm	IETF RFC 1321: The MD5 Message-Digest Algorithm	http://www.ietf.org/rfc/rfc1321.txt
RFC 1833: Binding Protocols for ONC RPC Version 2	IETF RFC 1833: Binding Protocols for ONC RPC Version 2	http://www.ietf.org/rfc/rfc1833.txt
RFC 1951: DEFLATE Compressed Data Format Specification	IETF RFC 1951: DEFLATE Compressed Data Format Specification version 1.3	http://www.ietf.org/rfc/rfc1951.txt
RFC 1952: GZIP File Format Specification	IETF RFC 1952: GZIP file format specification version 4.3	http://www.ietf.org/rfc/rfc1952.txt
RFC 2440: OpenPGP Message Format	IETF RFC 2440: OpenPGP Message Format	http://www.ietf.org/rfc/rfc2440.txt
SUSv2	CAE Specification, January 1997, System Interfaces and Headers (XSH),Issue 5 (ISBN: 1-85912-181-0, C606)	http://www.opengroup.org/publications/catalog/un.htm
SUSv2 Command and Utilities	The Single UNIXŽ Specification(SUS) Version 2, Commands and Utilities (XCU), Issue 5 (ISBN: 1-85912-191-8, C604)	http://www.opengroup.org/publications/catalog/un.htm
SVID Issue 3	American Telephone and Telegraph Company, System V Interface Definition, Issue 3 ; Morristown, NJ, UNIX Press, 1989.(ISBN 0201566524)
SVID Issue 4	System V Interface Definition,Fourth Edition
System V ABI	System V Application Binary Interface, Edition 4.1	http://www.caldera.com/developers/devspecs/gabi41.pdf
System V ABI Update	System V Application Binary Interface - DRAFT - 17 December 2003	http://www.caldera.com/developers/gabi/2003-12-17/contents.html
The PowerPC ™ Architecture	The PowerPC ™ Architecture: A Specification for a new family of RISC processors	http://www.austin.ibm.com
The PowerPC ™ Architecture, Book I Changes	The PowerPC Architecture Book I changes	http://www-1.ibm.com/servers/eserver/pseries/library/ppc_chg1.html
The PowerPC ™ Architecture, Book II Changes	The PowerPC Architecture Book II changes	http://www-1.ibm.com/servers/eserver/pseries/library/ppc_chg2.html
The PowerPC ™ Architecture, Book III Changes	The PowerPC Architecture Book III changes	http://www-1.ibm.com/servers/eserver/pseries/library/ppc_chg3.html
this specification	Linux Standard Base	http://www.linuxbase.org/spec/
X/Open Curses	CAE Specification, May 1996, X/Open Curses, Issue 4, Version 2 (ISBN: 1-85912-171-3, C610), plus Corrigendum U018	http://www.opengroup.org/publications/catalog/un.htm
zlib Manual	zlib 1.2 Manual	http://www.gzip.org/zlib/

Chapter 3. Requirements

Relevant Libraries

The libraries listed in Table 3-1 shall be available on PPC64 Linux Standard Base systems, with the specified runtime names. These names override or supplement the names specified in the generic LSB specification. The specified program interpreter, referred to as proginterp in this table, shall be used to load the shared libraries specified by DT_NEEDED entries at run time.

Table 3-1. Standard Library Names

Library	Runtime Name
libm	libm.so.6
libdl	libdl.so.2
libcrypt	libcrypt.so.1
libc	libc.so.6
libpthread	libpthread.so.0
proginterp	/lib64/ld-lsb-ppc64.so.2
libgcc_s	libgcc_s.so.1
libncurses	libncurses.so.5
libz	libz.so.1
libutil	libutil.so.1

These libraries will be in an implementation-defined directory which the dynamic linker shall search by default.

LSB Implementation Conformance

A conforming implementation shall satisfy the following requirements:

The implementation shall implement fully the architecture described in the hardware manual for the target processor architecture.
The implementation shall be capable of executing compiled applications having the format and using the system interfaces described in this document.
The implementation shall provide libraries containing the interfaces specified by this document, and shall provide a dynamic linking mechanism that allows these interfaces to be attached to applications at runtime. All the interfaces shall behave as specified in this document.
The map of virtual memory provided by the implementation shall conform to the requirements of this document.
The implementation's low-level behavior with respect to function call linkage, system traps, signals, and other such activities shall conform to the formats described in this document.
The implementation shall provide all of the mandatory interfaces in their entirety.
The implementation may provide one or more of the optional interfaces. Each optional interface that is provided shall be provided in its entirety. The product documentation shall state which optional interfaces are provided.
The implementation shall provide all files and utilities specified as part of this document in the format defined here and in other referenced documents. All commands and utilities shall behave as required by this document. The implementation shall also provide all mandatory components of an application's runtime environment that are included or referenced in this document.
The implementation, when provided with standard data formats and values at a named interface, shall provide the behavior defined for those values and data formats at that interface. However, a conforming implementation may consist of components which are separately packaged and/or sold. For example, a vendor of a conforming implementation might sell the hardware, operating system, and windowing system as separately packaged items.
The implementation may provide additional interfaces with different names. It may also provide additional behavior corresponding to data values outside the standard ranges, for standard named interfaces.

LSB Application Conformance

A conforming application shall satisfy the following requirements:

Its executable files are either shell scripts or object files in the format defined for the Object File Format system interface.
Its object files participate in dynamic linking as defined in the Program Loading and Linking System interface.
It employs only the instructions, traps, and other low-level facilities defined in the Low-Level System interface as being for use by applications.
If it requires any optional interface defined in this document in order to be installed or to execute successfully, the requirement for that optional interface is stated in the application's documentation.
It does not use any interface or data format that is not required to be provided by a conforming implementation, unless:
- If such an interface or data format is supplied by another application through direct invocation of that application during execution, that application is in turn an LSB conforming application.
- The use of that interface or data format, as well as its source, is identified in the documentation of the application.
It shall not use any values for a named interface that are reserved for vendor extensions.

A strictly conforming application does not require or use any interface, facility, or implementation-defined extension that is not defined in this document in order to be installed or to execute successfully.

Chapter 4. Definitions

For the purposes of this document, the following definitions, as specified in the ISO/IEC Directives, Part 2, 2001, 4th Edition, apply:

can: be able to; there is a possibility of; it is possible to
cannot: be unable to; there is no possibilty of; it is not possible to
may: is permitted; is allowed; is permissible
need not: it is not required that; no...is required
shall: is to; is required to; it is required that; has to; only...is permitted; it is necessary
shall not: is not allowed [permitted] [acceptable] [permissible]; is required to be not; is required that...be not; is not to be
should: it is recommended that; ought to
should not: it is not recommended that; ought not to

Chapter 5. Terminology

For the purposes of this document, the following terms apply:

archLSB: The architectural part of the LSB Specification which describes the specific parts of the interface that are platform specific. The archLSB is complementary to the gLSB.
Binary Standard: The total set of interfaces that are available to be used in the compiled binary code of a conforming application.
gLSB: The common part of the LSB Specification that describes those parts of the interface that remain constant across all hardware implementations of the LSB.
implementation-defined: Describes a value or behavior that is not defined by this document but is selected by an implementor. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence of the value or behavior. An application that relies on such a value or behavior cannot be assured to be portable across conforming implementations. The implementor shall document such a value or behavior so that it can be used correctly by an application.
Shell Script: A file that is read by an interpreter (e.g., awk). The first line of the shell script includes a reference to its interpreter binary.
Source Standard: The set of interfaces that are available to be used in the source code of a conforming application.
undefined: Describes the nature of a value or behavior not defined by this document which results from use of an invalid program construct or invalid data input. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence or validity of the value or behavior. An application that relies on any particular value or behavior cannot be assured to be portable across conforming implementations.
unspecified: Describes the nature of a value or behavior not specified by this document which results from use of a valid program construct or valid data input. The value or behavior may vary among implementations that conform to this document. An application should not rely on the existence or validity of the value or behavior. An application that relies on any particular value or behavior cannot be assured to be portable across conforming implementations.

Other terms and definitions used in this document shall have the same meaning as defined in Chapter 3 of the Base Definitions volume of ISO POSIX (2003).

Chapter 6. Documentation Conventions

Throughout this document, the following typographic conventions are used:

function(): the name of a function
command: the name of a command or utility
CONSTANT: a constant value
parameter: a parameter
variable: a variable

Throughout this specification, several tables of interfaces are presented. Each entry in these tables has the following format:

name: the name of the interface
(symver): An optional symbol version identifier, if required.
[refno]: A reference number indexing the table of referenced specifications that follows this table.

For example,

forkpty(GLIBC_2.0) [1]

refers to the interface named forkpty with symbol version GLIBC_2.0 that is defined in the first of the listed references below the table.

ELF Specification

Table of Contents

I. Low Level System Information

1. Machine Interface

Processor Architecture
Data Representation
Byte Ordering
Fundamental Types
Aggregates and Unions
Bit Fields

2. Function Calling Sequence

Registers
Stack Frame
Parameter Passing
Return Values
Function Descriptors

3. Traceback Tables

Mandatory Fields
Optional Fields

4. Process Initialization

Registers
Process Stack

5. Coding Examples

Code Model Overview
The TOC Section
TOC Assembly Language Syntax
Function Prologue and Epilogue
Register Saving and Restoring Functions
Saving General Registers Only
Saving General Registers and Floating Point Registers
Saving Floating Point Registers Only
Save and Restore Services
Data Objects
Function Calls
Branching
Dynamic Stack Space Allocation

II. Object Format

6. ELF Header

7. Special Sections

8. TOC

9. Symbol Table

Symbol Values

10. Relocation

Relocation Types

III. Program Loading and Dynamic Linking

11. Program Loading

12. Dynamic Linking

Dynamic Section
Global Offset Table
Function Addresses
Procedure Linkage Table

List of Tables
7-1. ELF Special Sections

I. Low Level System Information

Table of Contents
1. Machine Interface
2. Function Calling Sequence
3. Traceback Tables
4. Process Initialization
5. Coding Examples

Chapter 1. Machine Interface

Processor Architecture

The PowerPC Architecture is specified by the following documents:

64-bit PowerPC ELF ABI Supplement
The PowerPC ™ Architecture
The PowerPC ™ Architecture, Book I Changes
The PowerPC ™ Architecture, Book II Changes
The PowerPC ™ Architecture, Book III Changes

Only the features of the PowerPC processor instruction set may be assumed to be present. An application is responsible for determining if any additional instruction set features are available before using those additional features. If a feature is not present, then the application may not use it.

Only instructions which do not require elevated privileges may be used.

Applications may not make system calls directly. The interfaces in the C library must be used instead.

An implementation must support the 64-bit computation mode as described in The PowerPC ™ Architecture.

Applications conforming to this specification must provide feedback to the user if a feature that is required for correct execution of the application is not present. Applications conforming to this specification should attempt to execute in a diminished capacity if a required feature is not present.

This specification does not provide any performance guarantees of a conforming system. A system conforming to this specification may be implemented in either hardware or software.

Data Representation

LSB-conforming applications shall use the data representation as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Byte Ordering

LSB-conforming applications shall use big-endian byte ordering. LSB-conforming implementations may support little-endian applications.

Fundamental Types

LSB-conforming applications shall use the fundamental types as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

LSB-conforming applications shall not use the long double fundamental type.

Aggregates and Unions

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Bit Fields

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Chapter 2. Function Calling Sequence

LSB-conforming applications shall use the function calling sequence as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Registers

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Stack Frame

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Parameter Passing

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Return Values

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Function Descriptors

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Chapter 3. Traceback Tables

LSB-conforming applications shall use the traceback tables as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Mandatory Fields

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Optional Fields

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Chapter 4. Process Initialization

LSB-conforming applications shall use the Operating System Interfaces as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Registers

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Process Stack

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Chapter 5. Coding Examples

LSB-conforming applications may implement fundamental operations using the Coding Examples as defined in Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Code Model Overview

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

The TOC Section

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

TOC Assembly Language Syntax

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Function Prologue and Epilogue

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Register Saving and Restoring Functions

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Saving General Registers Only

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Saving General Registers and Floating Point Registers

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Saving Floating Point Registers Only

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Save and Restore Services

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Data Objects

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Function Calls

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Branching

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

Dynamic Stack Space Allocation

See Chapter 3 of the 64-bit PowerPC ELF ABI Supplement.

II. Object Format

LSB-conforming implementations shall support an object file , called Executable and Linking Format (ELF) as defined by the 64-bit PowerPC ELF ABI Supplement and as supplemented by the Linux Standard Base Specification and this document. LSB-conforming implementations need not support tags related functionality. LSB-conforming applications must not rely on tags related functionality.

Table of Contents
6. ELF Header
7. Special Sections
8. TOC
9. Symbol Table
10. Relocation

Chapter 6. ELF Header

LSB-conforming applications shall use the ELF header as defined in 64-bit PowerPC ELF ABI Supplement, Chapter 4.

Chapter 7. Special Sections

The following sections are defined in the 64-bit PowerPC ELF ABI Supplement.

Table 7-1. ELF Special Sections

Name	Type	Attributes
.glink	SHT_PROGBITS	SHF_ALLOC+SHF_EXECINSTR
.got	SHT_PROGBITS	SHF_ALLOC+SHF_WRITE
.plt	SHT_NOBITS	SHF_ALLOC+SHF_WRITE
.sbss	SHT_NOBITS	SHF_ALLOC+SHF_WRITE
.sdata	SHT_PROGBITS	SHF_ALLOC+SHF_WRITE
.toc	SHT_PROGBITS	SHF_ALLOC+SHF_WRITE
.tocbss	SHT_NOBITS	SHF_ALLOC+SHF_WRITE

.glink: This section may be used to hold the global linkage table which aids the procedure linkage table. See Procedure Linkage Table in Chapter 5 of the processor supplement for more information
.got: This section may be used to hold the Global Offset Table, or GOT. See The Toc Section and Coding Examples in Chapter 3 and Global Offset Table in Chapter 5 of the processor supplement for more information
.plt: This section holds the procedure linkage table. See Procedure Linkage Table in Chapter 5 of the processor supplement for more information
.sbss: This section holds uninitialized data that contribute to the program's memory image. The system initializes the data with zeroes when the program begins to run.
.sdata: This section holds initialized small data that contribute to the program memory image.
.toc: This section may be used to hold the initialized Table of Contents, or TOC
.tocbss: This section may be used to hold the uninitialized portions of the TOC. This data may also be stored as zero-initialized data in a .toc section

Chapter 8. TOC

LSB-conforming applications shall use the Table of Contents (TOC) as defined in 64-bit PowerPC ELF ABI Supplement, Chapter 4.

Chapter 9. Symbol Table

LSB-conforming applications shall use the Symbol Table as defined in Chapter 4 of the 64-bit PowerPC ELF ABI Supplement.

Symbol Values

See Chapter 4 of the 64-bit PowerPC ELF ABI Supplement.

Chapter 10. Relocation

LSB-conforming applications shall use Relocations as defined in Chapter 4 of the 64-bit PowerPC ELF ABI Supplement.

Relocation Types

See Chapter 4 of the 64-bit PowerPC ELF ABI Supplement.

III. Program Loading and Dynamic Linking

LSB-conforming implementations shall support the object file information and system actions that create running programs as specified in the System V ABI, 64-bit PowerPC ELF ABI Supplement and as supplemented by the Linux Standard Base Specification and this document.

Table of Contents
11. Program Loading
12. Dynamic Linking

Chapter 11. Program Loading

See 64-bit PowerPC ELF ABI Supplement, Chapter 5.1.

Chapter 12. Dynamic Linking

See 64-bit PowerPC ELF ABI Supplement, Chapter 5.2.

Dynamic Section

The following dynamic entries are defined in the 64-bit PowerPC ELF ABI Supplement, Chapter 5.2.

DT_JMPREL: This entry is associated with a table of relocation entries for the procedure linkage table. This entry is mandatory both for executable and shared object files
DT_PLTGOT: This entry's d_ptr member gives the address of the first byte in the procedure linkage table

In addtion the following dynamic entries are also supported:

DT_RELACOUNT: The number of relative relocations in .rela.dyn

Global Offset Table

See 64-bit PowerPC ELF ABI Supplement, Chapter 5.2.2.

Function Addresses

See 64-bit PowerPC ELF ABI Supplement, Chapter 5.2.3.

Procedure Linkage Table

See 64-bit PowerPC ELF ABI Supplement, Chapter 5.2.4.

Linux Standard Base Specification

List of Tables
1-1. libc Definition
1-2. libc - RPC Function Interfaces
1-3. libc - System Calls Function Interfaces
1-4. libc - Standard I/O Function Interfaces
1-5. libc - Standard I/O Data Interfaces
1-6. libc - Signal Handling Function Interfaces
1-7. libc - Signal Handling Data Interfaces
1-8. libc - Localization Functions Function Interfaces
1-9. libc - Localization Functions Data Interfaces
1-10. libc - Socket Interface Function Interfaces
1-11. libc - Socket Interface Deprecated Function Interfaces
1-12. libc - Wide Characters Function Interfaces
1-13. libc - String Functions Function Interfaces
1-14. libc - IPC Functions Function Interfaces
1-15. libc - Regular Expressions Function Interfaces
1-16. libc - Regular Expressions Deprecated Function Interfaces
1-17. libc - Regular Expressions Deprecated Data Interfaces
1-18. libc - Character Type Functions Function Interfaces
1-19. libc - Time Manipulation Function Interfaces
1-20. libc - Time Manipulation Deprecated Function Interfaces
1-21. libc - Time Manipulation Data Interfaces
1-22. libc - Terminal Interface Functions Function Interfaces
1-23. libc - System Database Interface Function Interfaces
1-24. libc - Language Support Function Interfaces
1-25. libc - Large File Support Function Interfaces
1-26. libc - Standard Library Function Interfaces
1-27. libc - Standard Library Data Interfaces
1-28. libm Definition
1-29. libm - Math Function Interfaces
1-30. libm - Math Data Interfaces
1-31. libpthread Definition
1-32. libpthread - Posix Threads Function Interfaces
1-33. libgcc_s Definition
1-34. libgcc_s - Unwind Library Function Interfaces
1-35. libdl Definition
1-36. libdl - Dynamic Loader Function Interfaces
1-37. libcrypt Definition
1-38. libcrypt - Encryption Function Interfaces
2-1. libz Definition
2-2. libncurses Definition
2-3. libutil Definition
2-4. libutil - Utility Functions Function Interfaces
A-1. libgcc_s Function Interfaces

I. Base Libraries

Table of Contents
1. Libraries

Chapter 1. Libraries

An LSB-conforming implementation shall support base libraries which provide interfaces for accessing the operating system, processor and other hardware in the system.

Only those interfaces that are unique to the PowerPC 64 platform are defined here. This section should be used in conjunction with the corresponding section in the Linux Standard Base Specification.

Program Interpreter/Dynamic Linker

The LSB specifies the Program Interpreter to be /lib64/ld-lsb-ppc64.so.2.

Interfaces for libc

Table 1-1 defines the library name and shared object name for the libc library

Table 1-1. libc Definition

Library:	libc
SONAME:	libc.so.6

The behavior of the interfaces in this library is specified by the following specifications:

RPC

Interfaces for RPC

An LSB conforming implementation shall provide the architecture specific functions for RPC specified in Table 1-2, with the full functionality as described in the referenced underlying specification.

Table 1-2. libc - RPC Function Interfaces

authnone_create(GLIBC_2.3) [1]	pmap_unset(GLIBC_2.3) [2]	svcerr_weakauth(GLIBC_2.3) [3]	xdr_float(GLIBC_2.3) [3]	xdr_u_char(GLIBC_2.3) [3]
clnt_create(GLIBC_2.3) [1]	setdomainname(GLIBC_2.3) [2]	svctcp_create(GLIBC_2.3) [2]	xdr_free(GLIBC_2.3) [3]	xdr_u_int(GLIBC_2.3) [2]
clnt_pcreateerror(GLIBC_2.3) [1]	svc_getreqset(GLIBC_2.3) [3]	svcudp_create(GLIBC_2.3) [2]	xdr_int(GLIBC_2.3) [3]	xdr_u_long(GLIBC_2.3) [3]
clnt_perrno(GLIBC_2.3) [1]	svc_register(GLIBC_2.3) [2]	xdr_accepted_reply(GLIBC_2.3) [3]	xdr_long(GLIBC_2.3) [3]	xdr_u_short(GLIBC_2.3) [3]
clnt_perror(GLIBC_2.3) [1]	svc_run(GLIBC_2.3) [2]	xdr_array(GLIBC_2.3) [3]	xdr_opaque(GLIBC_2.3) [3]	xdr_union(GLIBC_2.3) [3]
clnt_spcreateerror(GLIBC_2.3) [1]	svc_sendreply(GLIBC_2.3) [2]	xdr_bool(GLIBC_2.3) [3]	xdr_opaque_auth(GLIBC_2.3) [3]	xdr_vector(GLIBC_2.3) [3]
clnt_sperrno(GLIBC_2.3) [1]	svcerr_auth(GLIBC_2.3) [3]	xdr_bytes(GLIBC_2.3) [3]	xdr_pointer(GLIBC_2.3) [3]	xdr_void(GLIBC_2.3) [3]
clnt_sperror(GLIBC_2.3) [1]	svcerr_decode(GLIBC_2.3) [3]	xdr_callhdr(GLIBC_2.3) [3]	xdr_reference(GLIBC_2.3) [3]	xdr_wrapstring(GLIBC_2.3) [3]
getdomainname(GLIBC_2.3) [2]	svcerr_noproc(GLIBC_2.3) [3]	xdr_callmsg(GLIBC_2.3) [3]	xdr_rejected_reply(GLIBC_2.3) [3]	xdrmem_create(GLIBC_2.3) [3]
key_decryptsession(GLIBC_2.3) [3]	svcerr_noprog(GLIBC_2.3) [3]	xdr_char(GLIBC_2.3) [3]	xdr_replymsg(GLIBC_2.3) [3]	xdrrec_create(GLIBC_2.3) [3]
pmap_getport(GLIBC_2.3) [2]	svcerr_progvers(GLIBC_2.3) [3]	xdr_double(GLIBC_2.3) [3]	xdr_short(GLIBC_2.3) [3]	xdrrec_eof(GLIBC_2.3) [3]
pmap_set(GLIBC_2.3) [2]	svcerr_systemerr(GLIBC_2.3) [3]	xdr_enum(GLIBC_2.3) [3]	xdr_string(GLIBC_2.3) [3]

Referenced Specification(s)

[1]. SVID Issue 4

[2]. this specification

[3]. SVID Issue 3

System Calls

Interfaces for System Calls

An LSB conforming implementation shall provide the architecture specific functions for System Calls specified in Table 1-3, with the full functionality as described in the referenced underlying specification.

Table 1-3. libc - System Calls Function Interfaces

__fxstat(GLIBC_2.3) [1]	fchmod(GLIBC_2.3) [2]	getwd(GLIBC_2.3) [2]	read(GLIBC_2.3) [2]	setrlimit(GLIBC_2.3) [2]
__getpgid(GLIBC_2.3) [1]	fchown(GLIBC_2.3) [2]	initgroups(GLIBC_2.3) [1]	readdir(GLIBC_2.3) [2]	setrlimit64(GLIBC_2.3) [3]
__lxstat(GLIBC_2.3) [1]	fcntl(GLIBC_2.3) [1]	ioctl(GLIBC_2.3) [1]	readdir_r(GLIBC_2.3) [2]	setsid(GLIBC_2.3) [2]
__xmknod(GLIBC_2.3) [1]	fdatasync(GLIBC_2.3) [2]	kill(GLIBC_2.3) [1]	readlink(GLIBC_2.3) [2]	setuid(GLIBC_2.3) [2]
__xstat(GLIBC_2.3) [1]	flock(GLIBC_2.3) [1]	killpg(GLIBC_2.3) [2]	readv(GLIBC_2.3) [2]	sleep(GLIBC_2.3) [2]
access(GLIBC_2.3) [2]	fork(GLIBC_2.3) [2]	lchown(GLIBC_2.3) [2]	rename(GLIBC_2.3) [2]	statvfs(GLIBC_2.3) [2]
acct(GLIBC_2.3) [1]	fstatvfs(GLIBC_2.3) [2]	link(GLIBC_2.3) [2]	rmdir(GLIBC_2.3) [2]	stime(GLIBC_2.3) [1]
alarm(GLIBC_2.3) [2]	fsync(GLIBC_2.3) [2]	lockf(GLIBC_2.3) [2]	sbrk(GLIBC_2.3) [4]	symlink(GLIBC_2.3) [2]
brk(GLIBC_2.3) [4]	ftime(GLIBC_2.3) [2]	lseek(GLIBC_2.3) [2]	sched_get_priority_max(GLIBC_2.3) [2]	sync(GLIBC_2.3) [2]
chdir(GLIBC_2.3) [2]	ftruncate(GLIBC_2.3) [2]	mkdir(GLIBC_2.3) [2]	sched_get_priority_min(GLIBC_2.3) [2]	sysconf(GLIBC_2.3) [2]
chmod(GLIBC_2.3) [2]	getcontext(GLIBC_2.3) [2]	mkfifo(GLIBC_2.3) [2]	sched_getparam(GLIBC_2.3) [2]	time(GLIBC_2.3) [2]
chown(GLIBC_2.3) [2]	getegid(GLIBC_2.3) [2]	mlock(GLIBC_2.3) [2]	sched_getscheduler(GLIBC_2.3) [2]	times(GLIBC_2.3) [2]
chroot(GLIBC_2.3) [4]	geteuid(GLIBC_2.3) [2]	mlockall(GLIBC_2.3) [2]	sched_rr_get_interval(GLIBC_2.3) [2]	truncate(GLIBC_2.3) [2]
clock(GLIBC_2.3) [2]	getgid(GLIBC_2.3) [2]	mmap(GLIBC_2.3) [2]	sched_setparam(GLIBC_2.3) [2]	ulimit(GLIBC_2.3) [2]
close(GLIBC_2.3) [2]	getgroups(GLIBC_2.3) [2]	mprotect(GLIBC_2.3) [2]	sched_setscheduler(GLIBC_2.3) [2]	umask(GLIBC_2.3) [2]
closedir(GLIBC_2.3) [2]	getitimer(GLIBC_2.3) [2]	msync(GLIBC_2.3) [2]	sched_yield(GLIBC_2.3) [2]	uname(GLIBC_2.3) [2]
creat(GLIBC_2.3) [1]	getloadavg(GLIBC_2.3) [1]	munlock(GLIBC_2.3) [2]	select(GLIBC_2.3) [2]	unlink(GLIBC_2.3) [1]
dup(GLIBC_2.3) [2]	getpagesize(GLIBC_2.3) [4]	munlockall(GLIBC_2.3) [2]	setcontext(GLIBC_2.3) [2]	utime(GLIBC_2.3) [2]
dup2(GLIBC_2.3) [2]	getpgid(GLIBC_2.3) [2]	munmap(GLIBC_2.3) [2]	setegid(GLIBC_2.3) [2]	utimes(GLIBC_2.3) [2]
execl(GLIBC_2.3) [2]	getpgrp(GLIBC_2.3) [2]	nanosleep(GLIBC_2.3) [2]	seteuid(GLIBC_2.3) [2]	vfork(GLIBC_2.3) [2]
execle(GLIBC_2.3) [2]	getpid(GLIBC_2.3) [2]	nice(GLIBC_2.3) [2]	setgid(GLIBC_2.3) [2]	wait(GLIBC_2.3) [2]
execlp(GLIBC_2.3) [2]	getppid(GLIBC_2.3) [2]	open(GLIBC_2.3) [1]	setitimer(GLIBC_2.3) [2]	wait3(GLIBC_2.3) [1]
execv(GLIBC_2.3) [2]	getpriority(GLIBC_2.3) [2]	opendir(GLIBC_2.3) [2]	setpgid(GLIBC_2.3) [2]	wait4(GLIBC_2.3) [1]
execve(GLIBC_2.3) [2]	getrlimit(GLIBC_2.3) [2]	pathconf(GLIBC_2.3) [2]	setpgrp(GLIBC_2.3) [2]	waitpid(GLIBC_2.3) [1]
execvp(GLIBC_2.3) [2]	getrusage(GLIBC_2.3) [2]	pause(GLIBC_2.3) [2]	setpriority(GLIBC_2.3) [2]	write(GLIBC_2.3) [2]
exit(GLIBC_2.3) [2]	getsid(GLIBC_2.3) [2]	pipe(GLIBC_2.3) [2]	setregid(GLIBC_2.3) [2]	writev(GLIBC_2.3) [2]
fchdir(GLIBC_2.3) [2]	getuid(GLIBC_2.3) [2]	poll(GLIBC_2.3) [2]	setreuid(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

[3]. Large File Support

[4]. SUSv2

Standard I/O

Interfaces for Standard I/O

An LSB conforming implementation shall provide the architecture specific functions for Standard I/O specified in Table 1-4, with the full functionality as described in the referenced underlying specification.

Table 1-4. libc - Standard I/O Function Interfaces

_IO_feof(GLIBC_2.3) [1]	fgetpos(GLIBC_2.3) [2]	fsetpos(GLIBC_2.3) [2]	putchar(GLIBC_2.3) [2]	sscanf(GLIBC_2.3) [2]
_IO_getc(GLIBC_2.3) [1]	fgets(GLIBC_2.3) [2]	ftell(GLIBC_2.3) [2]	putchar_unlocked(GLIBC_2.3) [2]	telldir(GLIBC_2.3) [2]
_IO_putc(GLIBC_2.3) [1]	fgetwc_unlocked(GLIBC_2.3) [1]	ftello(GLIBC_2.3) [2]	puts(GLIBC_2.3) [2]	tempnam(GLIBC_2.3) [2]
_IO_puts(GLIBC_2.3) [1]	fileno(GLIBC_2.3) [2]	fwrite(GLIBC_2.3) [2]	putw(GLIBC_2.3) [3]	ungetc(GLIBC_2.3) [2]
asprintf(GLIBC_2.3) [1]	flockfile(GLIBC_2.3) [2]	getc(GLIBC_2.3) [2]	remove(GLIBC_2.3) [2]	vasprintf(GLIBC_2.3) [1]
clearerr(GLIBC_2.3) [2]	fopen(GLIBC_2.3) [1]	getc_unlocked(GLIBC_2.3) [2]	rewind(GLIBC_2.3) [2]	vdprintf(GLIBC_2.3) [1]
ctermid(GLIBC_2.3) [2]	fprintf(GLIBC_2.3) [2]	getchar(GLIBC_2.3) [2]	rewinddir(GLIBC_2.3) [2]	vfprintf(GLIBC_2.3) [2]
fclose(GLIBC_2.3) [2]	fputc(GLIBC_2.3) [2]	getchar_unlocked(GLIBC_2.3) [2]	scanf(GLIBC_2.3) [2]	vprintf(GLIBC_2.3) [2]
fdopen(GLIBC_2.3) [2]	fputs(GLIBC_2.3) [2]	getw(GLIBC_2.3) [3]	seekdir(GLIBC_2.3) [2]	vsnprintf(GLIBC_2.3) [2]
feof(GLIBC_2.3) [2]	fread(GLIBC_2.3) [2]	pclose(GLIBC_2.3) [2]	setbuf(GLIBC_2.3) [2]	vsprintf(GLIBC_2.3) [2]
ferror(GLIBC_2.3) [2]	freopen(GLIBC_2.3) [1]	popen(GLIBC_2.3) [2]	setbuffer(GLIBC_2.3) [1]
fflush(GLIBC_2.3) [2]	fscanf(GLIBC_2.3) [2]	printf(GLIBC_2.3) [2]	setvbuf(GLIBC_2.3) [2]
fflush_unlocked(GLIBC_2.3) [1]	fseek(GLIBC_2.3) [2]	putc(GLIBC_2.3) [2]	snprintf(GLIBC_2.3) [2]
fgetc(GLIBC_2.3) [2]	fseeko(GLIBC_2.3) [2]	putc_unlocked(GLIBC_2.3) [2]	sprintf(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

[3]. SUSv2

An LSB conforming implementation shall provide the architecture specific data interfaces for Standard I/O specified in Table 1-5, with the full functionality as described in the referenced underlying specification.

Table 1-5. libc - Standard I/O Data Interfaces

stderr(GLIBC_2.3) [1]

stdin(GLIBC_2.3) [1]

stdout(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

Signal Handling

Interfaces for Signal Handling

An LSB conforming implementation shall provide the architecture specific functions for Signal Handling specified in Table 1-6, with the full functionality as described in the referenced underlying specification.

Table 1-6. libc - Signal Handling Function Interfaces

__libc_current_sigrtmax(GLIBC_2.3) [1]	sigaddset(GLIBC_2.3) [2]	sighold(GLIBC_2.3) [2]	sigpause(GLIBC_2.3) [2]	sigsuspend(GLIBC_2.3) [2]
__libc_current_sigrtmin(GLIBC_2.3) [1]	sigaltstack(GLIBC_2.3) [2]	sigignore(GLIBC_2.3) [2]	sigpending(GLIBC_2.3) [2]	sigtimedwait(GLIBC_2.3) [2]
__sigsetjmp(GLIBC_2.3) [1]	sigandset(GLIBC_2.3) [1]	siginterrupt(GLIBC_2.3) [2]	sigprocmask(GLIBC_2.3) [2]	sigwait(GLIBC_2.3) [2]
__sysv_signal(GLIBC_2.3) [1]	sigblock(GLIBC_2.3) [1]	sigisemptyset(GLIBC_2.3) [1]	sigqueue(GLIBC_2.3) [2]	sigwaitinfo(GLIBC_2.3) [2]
bsd_signal(GLIBC_2.3) [2]	sigdelset(GLIBC_2.3) [2]	sigismember(GLIBC_2.3) [2]	sigrelse(GLIBC_2.3) [2]
psignal(GLIBC_2.3) [1]	sigemptyset(GLIBC_2.3) [2]	siglongjmp(GLIBC_2.3) [2]	sigreturn(GLIBC_2.3) [1]
raise(GLIBC_2.3) [2]	sigfillset(GLIBC_2.3) [2]	signal(GLIBC_2.3) [2]	sigset(GLIBC_2.3) [2]
sigaction(GLIBC_2.3) [2]	siggetmask(GLIBC_2.3) [1]	sigorset(GLIBC_2.3) [1]	sigstack(GLIBC_2.3) [3]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

[3]. SUSv2

An LSB conforming implementation shall provide the architecture specific data interfaces for Signal Handling specified in Table 1-7, with the full functionality as described in the referenced underlying specification.

Table 1-7. libc - Signal Handling Data Interfaces

_sys_siglist(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. this specification

Localization Functions

Interfaces for Localization Functions

An LSB conforming implementation shall provide the architecture specific functions for Localization Functions specified in Table 1-8, with the full functionality as described in the referenced underlying specification.

Table 1-8. libc - Localization Functions Function Interfaces

bind_textdomain_codeset(GLIBC_2.3) [1]	catopen(GLIBC_2.3) [2]	dngettext(GLIBC_2.3) [1]	iconv_open(GLIBC_2.3) [2]	setlocale(GLIBC_2.3) [2]
bindtextdomain(GLIBC_2.3) [1]	dcgettext(GLIBC_2.3) [1]	gettext(GLIBC_2.3) [1]	localeconv(GLIBC_2.3) [2]	textdomain(GLIBC_2.3) [1]
catclose(GLIBC_2.3) [2]	dcngettext(GLIBC_2.3) [1]	iconv(GLIBC_2.3) [2]	ngettext(GLIBC_2.3) [1]
catgets(GLIBC_2.3) [2]	dgettext(GLIBC_2.3) [1]	iconv_close(GLIBC_2.3) [2]	nl_langinfo(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

An LSB conforming implementation shall provide the architecture specific data interfaces for Localization Functions specified in Table 1-9, with the full functionality as described in the referenced underlying specification.

Table 1-9. libc - Localization Functions Data Interfaces

_nl_msg_cat_cntr(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. this specification

Socket Interface

Interfaces for Socket Interface

An LSB conforming implementation shall provide the architecture specific functions for Socket Interface specified in Table 1-10, with the full functionality as described in the referenced underlying specification.

Table 1-10. libc - Socket Interface Function Interfaces

__h_errno_location(GLIBC_2.3) [1]	gethostid(GLIBC_2.3) [2]	listen(GLIBC_2.3) [2]	sendmsg(GLIBC_2.3) [2]	socketpair(GLIBC_2.3) [2]
accept(GLIBC_2.3) [2]	gethostname(GLIBC_2.3) [2]	recv(GLIBC_2.3) [2]	sendto(GLIBC_2.3) [2]
bind(GLIBC_2.3) [2]	getpeername(GLIBC_2.3) [2]	recvfrom(GLIBC_2.3) [2]	setsockopt(GLIBC_2.3) [1]
bindresvport(GLIBC_2.3) [1]	getsockname(GLIBC_2.3) [2]	recvmsg(GLIBC_2.3) [2]	shutdown(GLIBC_2.3) [2]
connect(GLIBC_2.3) [2]	getsockopt(GLIBC_2.3) [2]	send(GLIBC_2.3) [2]	socket(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

An LSB conforming implementation shall provide the architecture specific deprecated functions for Socket Interface specified in Table 1-11, with the full functionality as described in the referenced underlying specification.

Table 1-14. libc - IPC Functions Function Interfaces

ftok(GLIBC_2.3) [1]	msgrcv(GLIBC_2.3) [1]	semget(GLIBC_2.3) [1]	shmctl(GLIBC_2.3) [1]
msgctl(GLIBC_2.3) [1]	msgsnd(GLIBC_2.3) [1]	semop(GLIBC_2.3) [1]	shmdt(GLIBC_2.3) [1]
msgget(GLIBC_2.3) [1]	semctl(GLIBC_2.3) [1]	shmat(GLIBC_2.3) [1]	shmget(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

Regular Expressions

Interfaces for Regular Expressions

An LSB conforming implementation shall provide the architecture specific functions for Regular Expressions specified in Table 1-15, with the full functionality as described in the referenced underlying specification.

Table 1-15. libc - Regular Expressions Function Interfaces

regcomp(GLIBC_2.3) [1]

regerror(GLIBC_2.3) [1]

regexec(GLIBC_2.3) [1]

regfree(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

An LSB conforming implementation shall provide the architecture specific deprecated functions for Regular Expressions specified in Table 1-16, with the full functionality as described in the referenced underlying specification.

These interfaces are deprecated, and applications should avoid using them. These interfaces may be withdrawn in future releases of this specification.

Table 1-16. libc - Regular Expressions Deprecated Function Interfaces

advance(GLIBC_2.3) [1]

re_comp(GLIBC_2.3) [1]

re_exec(GLIBC_2.3) [1]

step(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. SUSv2

An LSB conforming implementation shall provide the architecture specific deprecated data interfaces for Regular Expressions specified in Table 1-17, with the full functionality as described in the referenced underlying specification.

These interfaces are deprecated, and applications should avoid using them. These interfaces may be withdrawn in future releases of this specification.

Table 1-17. libc - Regular Expressions Deprecated Data Interfaces

loc1(GLIBC_2.3) [1]

loc2(GLIBC_2.3) [1]

locs(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. SUSv2

Character Type Functions

Interfaces for Character Type Functions

An LSB conforming implementation shall provide the architecture specific functions for Character Type Functions specified in Table 1-18, with the full functionality as described in the referenced underlying specification.

Table 1-18. libc - Character Type Functions Function Interfaces

__ctype_get_mb_cur_max(GLIBC_2.3) [1]	isdigit(GLIBC_2.3) [2]	iswalnum(GLIBC_2.3) [2]	iswlower(GLIBC_2.3) [2]	toascii(GLIBC_2.3) [2]
_tolower(GLIBC_2.3) [2]	isgraph(GLIBC_2.3) [2]	iswalpha(GLIBC_2.3) [2]	iswprint(GLIBC_2.3) [2]	tolower(GLIBC_2.3) [2]
_toupper(GLIBC_2.3) [2]	islower(GLIBC_2.3) [2]	iswblank(GLIBC_2.3) [2]	iswpunct(GLIBC_2.3) [2]	toupper(GLIBC_2.3) [2]
isalnum(GLIBC_2.3) [2]	isprint(GLIBC_2.3) [2]	iswcntrl(GLIBC_2.3) [2]	iswspace(GLIBC_2.3) [2]
isalpha(GLIBC_2.3) [2]	ispunct(GLIBC_2.3) [2]	iswctype(GLIBC_2.3) [2]	iswupper(GLIBC_2.3) [2]
isascii(GLIBC_2.3) [2]	isspace(GLIBC_2.3) [2]	iswdigit(GLIBC_2.3) [2]	iswxdigit(GLIBC_2.3) [2]
iscntrl(GLIBC_2.3) [2]	isupper(GLIBC_2.3) [2]	iswgraph(GLIBC_2.3) [2]	isxdigit(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

Time Manipulation

Interfaces for Time Manipulation

An LSB conforming implementation shall provide the architecture specific functions for Time Manipulation specified in Table 1-19, with the full functionality as described in the referenced underlying specification.

Table 1-19. libc - Time Manipulation Function Interfaces

adjtime(GLIBC_2.3) [1]	ctime(GLIBC_2.3) [2]	gmtime(GLIBC_2.3) [2]	localtime_r(GLIBC_2.3) [2]	ualarm(GLIBC_2.3) [2]
asctime(GLIBC_2.3) [2]	ctime_r(GLIBC_2.3) [2]	gmtime_r(GLIBC_2.3) [2]	mktime(GLIBC_2.3) [2]
asctime_r(GLIBC_2.3) [2]	difftime(GLIBC_2.3) [2]	localtime(GLIBC_2.3) [2]	tzset(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

An LSB conforming implementation shall provide the architecture specific deprecated functions for Time Manipulation specified in Table 1-20, with the full functionality as described in the referenced underlying specification.

These interfaces are deprecated, and applications should avoid using them. These interfaces may be withdrawn in future releases of this specification.

Table 1-20. libc - Time Manipulation Deprecated Function Interfaces

adjtimex(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. this specification

An LSB conforming implementation shall provide the architecture specific data interfaces for Time Manipulation specified in Table 1-21, with the full functionality as described in the referenced underlying specification.

Table 1-21. libc - Time Manipulation Data Interfaces

__daylight(GLIBC_2.3) [1]	__tzname(GLIBC_2.3) [1]	timezone(GLIBC_2.3) [2]
__timezone(GLIBC_2.3) [1]	daylight(GLIBC_2.3) [2]	tzname(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

Terminal Interface Functions

Interfaces for Terminal Interface Functions

An LSB conforming implementation shall provide the architecture specific functions for Terminal Interface Functions specified in Table 1-22, with the full functionality as described in the referenced underlying specification.

Table 1-22. libc - Terminal Interface Functions Function Interfaces

cfgetispeed(GLIBC_2.3) [1]	cfsetispeed(GLIBC_2.3) [1]	tcdrain(GLIBC_2.3) [1]	tcgetattr(GLIBC_2.3) [1]	tcsendbreak(GLIBC_2.3) [1]
cfgetospeed(GLIBC_2.3) [1]	cfsetospeed(GLIBC_2.3) [1]	tcflow(GLIBC_2.3) [1]	tcgetpgrp(GLIBC_2.3) [1]	tcsetattr(GLIBC_2.3) [1]
cfmakeraw(GLIBC_2.3) [2]	cfsetspeed(GLIBC_2.3) [2]	tcflush(GLIBC_2.3) [1]	tcgetsid(GLIBC_2.3) [1]	tcsetpgrp(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

[2]. this specification

System Database Interface

Interfaces for System Database Interface

An LSB conforming implementation shall provide the architecture specific functions for System Database Interface specified in Table 1-23, with the full functionality as described in the referenced underlying specification.

Table 1-23. libc - System Database Interface Function Interfaces

endgrent(GLIBC_2.3) [1]	getgrgid(GLIBC_2.3) [1]	getprotobynumber(GLIBC_2.3) [1]	getservbyport(GLIBC_2.3) [1]	setgrent(GLIBC_2.3) [1]
endnetent(GLIBC_2.3) [1]	getgrgid_r(GLIBC_2.3) [1]	getprotoent(GLIBC_2.3) [1]	getservent(GLIBC_2.3) [1]	setgroups(GLIBC_2.3) [2]
endprotoent(GLIBC_2.3) [1]	getgrnam(GLIBC_2.3) [1]	getpwent(GLIBC_2.3) [1]	getutent(GLIBC_2.3) [2]	setnetent(GLIBC_2.3) [1]
endpwent(GLIBC_2.3) [1]	getgrnam_r(GLIBC_2.3) [1]	getpwnam(GLIBC_2.3) [1]	getutent_r(GLIBC_2.3) [2]	setprotoent(GLIBC_2.3) [1]
endservent(GLIBC_2.3) [1]	gethostbyaddr(GLIBC_2.3) [1]	getpwnam_r(GLIBC_2.3) [1]	getutxent(GLIBC_2.3) [1]	setpwent(GLIBC_2.3) [1]
endutent(GLIBC_2.3) [3]	gethostbyname(GLIBC_2.3) [1]	getpwuid(GLIBC_2.3) [1]	getutxid(GLIBC_2.3) [1]	setservent(GLIBC_2.3) [1]
endutxent(GLIBC_2.3) [1]	getnetbyaddr(GLIBC_2.3) [1]	getpwuid_r(GLIBC_2.3) [1]	getutxline(GLIBC_2.3) [1]	setutent(GLIBC_2.3) [2]
getgrent(GLIBC_2.3) [1]	getprotobyname(GLIBC_2.3) [1]	getservbyname(GLIBC_2.3) [1]	pututxline(GLIBC_2.3) [1]	setutxent(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

[2]. this specification

[3]. SUSv2

Language Support

Interfaces for Language Support

An LSB conforming implementation shall provide the architecture specific functions for Language Support specified in Table 1-24, with the full functionality as described in the referenced underlying specification.

Table 1-24. libc - Language Support Function Interfaces

__libc_start_main(GLIBC_2.3) [1]

_obstack_begin(GLIBC_2.3) [1]

_obstack_newchunk(GLIBC_2.3) [1]

obstack_free(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. this specification

Large File Support

Interfaces for Large File Support

An LSB conforming implementation shall provide the architecture specific functions for Large File Support specified in Table 1-25, with the full functionality as described in the referenced underlying specification.

Table 1-25. libc - Large File Support Function Interfaces

__fxstat64(GLIBC_2.3) [1]	fopen64(GLIBC_2.3) [2]	ftello64(GLIBC_2.3) [2]	lseek64(GLIBC_2.3) [2]	readdir64(GLIBC_2.3) [2]
__lxstat64(GLIBC_2.3) [1]	freopen64(GLIBC_2.3) [2]	ftruncate64(GLIBC_2.3) [2]	mkstemp64(GLIBC_2.3) [2]	statvfs64(GLIBC_2.3) [2]
__xstat64(GLIBC_2.3) [1]	fseeko64(GLIBC_2.3) [2]	ftw64(GLIBC_2.3) [2]	mmap64(GLIBC_2.3) [2]	tmpfile64(GLIBC_2.3) [2]
creat64(GLIBC_2.3) [2]	fsetpos64(GLIBC_2.3) [2]	getrlimit64(GLIBC_2.3) [2]	nftw64(GLIBC_2.3) [2]	truncate64(GLIBC_2.3) [2]
fgetpos64(GLIBC_2.3) [2]	fstatvfs64(GLIBC_2.3) [2]	lockf64(GLIBC_2.3) [2]	open64(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. Large File Support

Standard Library

Interfaces for Standard Library

An LSB conforming implementation shall provide the architecture specific functions for Standard Library specified in Table 1-26, with the full functionality as described in the referenced underlying specification.

Table 1-26. libc - Standard Library Function Interfaces

_Exit(GLIBC_2.3) [1]	dirname(GLIBC_2.3) [1]	glob(GLIBC_2.3) [1]	lsearch(GLIBC_2.3) [1]	srand(GLIBC_2.3) [1]
__assert_fail(GLIBC_2.3) [2]	div(GLIBC_2.3) [1]	glob64(GLIBC_2.3) [2]	makecontext(GLIBC_2.3) [1]	srand48(GLIBC_2.3) [1]
__cxa_atexit(GLIBC_2.3) [2]	drand48(GLIBC_2.3) [1]	globfree(GLIBC_2.3) [1]	malloc(GLIBC_2.3) [1]	srandom(GLIBC_2.3) [1]
__errno_location(GLIBC_2.3) [2]	ecvt(GLIBC_2.3) [1]	globfree64(GLIBC_2.3) [2]	memmem(GLIBC_2.3) [2]	strtod(GLIBC_2.3) [1]
__fpending(GLIBC_2.3) [2]	erand48(GLIBC_2.3) [1]	grantpt(GLIBC_2.3) [1]	mkstemp(GLIBC_2.3) [1]	strtol(GLIBC_2.3) [1]
__getpagesize(GLIBC_2.3) [2]	err(GLIBC_2.3) [2]	hcreate(GLIBC_2.3) [1]	mktemp(GLIBC_2.3) [1]	strtoul(GLIBC_2.3) [1]
__isinf(GLIBC_2.3) [2]	error(GLIBC_2.3) [2]	hdestroy(GLIBC_2.3) [1]	mrand48(GLIBC_2.3) [1]	swapcontext(GLIBC_2.3) [1]
__isinff(GLIBC_2.3) [2]	errx(GLIBC_2.3) [2]	hsearch(GLIBC_2.3) [1]	nftw(GLIBC_2.3) [1]	syslog(GLIBC_2.3) [1]
__isinfl(GLIBC_2.3) [2]	fcvt(GLIBC_2.3) [1]	htonl(GLIBC_2.3) [1]	nrand48(GLIBC_2.3) [1]	system(GLIBC_2.3) [2]
__isnan(GLIBC_2.3) [2]	fmtmsg(GLIBC_2.3) [1]	htons(GLIBC_2.3) [1]	ntohl(GLIBC_2.3) [1]	tdelete(GLIBC_2.3) [1]
__isnanf(GLIBC_2.3) [2]	fnmatch(GLIBC_2.3) [1]	imaxabs(GLIBC_2.3) [1]	ntohs(GLIBC_2.3) [1]	tfind(GLIBC_2.3) [1]
__isnanl(GLIBC_2.3) [2]	fpathconf(GLIBC_2.3) [1]	imaxdiv(GLIBC_2.3) [1]	openlog(GLIBC_2.3) [1]	tmpfile(GLIBC_2.3) [1]
__sysconf(GLIBC_2.3) [2]	free(GLIBC_2.3) [1]	inet_addr(GLIBC_2.3) [1]	perror(GLIBC_2.3) [1]	tmpnam(GLIBC_2.3) [1]
_exit(GLIBC_2.3) [1]	freeaddrinfo(GLIBC_2.3) [1]	inet_ntoa(GLIBC_2.3) [1]	posix_memalign(GLIBC_2.3) [1]	tsearch(GLIBC_2.3) [1]
_longjmp(GLIBC_2.3) [1]	ftrylockfile(GLIBC_2.3) [1]	inet_ntop(GLIBC_2.3) [1]	ptsname(GLIBC_2.3) [1]	ttyname(GLIBC_2.3) [1]
_setjmp(GLIBC_2.3) [1]	ftw(GLIBC_2.3) [1]	inet_pton(GLIBC_2.3) [1]	putenv(GLIBC_2.3) [1]	ttyname_r(GLIBC_2.3) [1]
a64l(GLIBC_2.3) [1]	funlockfile(GLIBC_2.3) [1]	initstate(GLIBC_2.3) [1]	qsort(GLIBC_2.3) [1]	twalk(GLIBC_2.3) [1]
abort(GLIBC_2.3) [1]	gai_strerror(GLIBC_2.3) [1]	insque(GLIBC_2.3) [1]	rand(GLIBC_2.3) [1]	unlockpt(GLIBC_2.3) [1]
abs(GLIBC_2.3) [1]	gcvt(GLIBC_2.3) [1]	isatty(GLIBC_2.3) [1]	rand_r(GLIBC_2.3) [1]	unsetenv(GLIBC_2.3) [1]
atof(GLIBC_2.3) [1]	getaddrinfo(GLIBC_2.3) [1]	isblank(GLIBC_2.3) [1]	random(GLIBC_2.3) [1]	usleep(GLIBC_2.3) [1]
atoi(GLIBC_2.3) [1]	getcwd(GLIBC_2.3) [1]	jrand48(GLIBC_2.3) [1]	random_r(GLIBC_2.3) [2]	verrx(GLIBC_2.3) [2]
atol(GLIBC_2.3) [1]	getdate(GLIBC_2.3) [1]	l64a(GLIBC_2.3) [1]	realloc(GLIBC_2.3) [1]	vfscanf(GLIBC_2.3) [1]
atoll(GLIBC_2.3) [1]	getenv(GLIBC_2.3) [1]	labs(GLIBC_2.3) [1]	realpath(GLIBC_2.3) [1]	vscanf(GLIBC_2.3) [1]
basename(GLIBC_2.3) [1]	getlogin(GLIBC_2.3) [1]	lcong48(GLIBC_2.3) [1]	remque(GLIBC_2.3) [1]	vsscanf(GLIBC_2.3) [1]
bsearch(GLIBC_2.3) [1]	getnameinfo(GLIBC_2.3) [1]	ldiv(GLIBC_2.3) [1]	seed48(GLIBC_2.3) [1]	vsyslog(GLIBC_2.3) [2]
calloc(GLIBC_2.3) [1]	getopt(GLIBC_2.3) [2]	lfind(GLIBC_2.3) [1]	setenv(GLIBC_2.3) [1]	warn(GLIBC_2.3) [2]
closelog(GLIBC_2.3) [1]	getopt_long(GLIBC_2.3) [2]	llabs(GLIBC_2.3) [1]	sethostid(GLIBC_2.3) [2]	warnx(GLIBC_2.3) [2]
confstr(GLIBC_2.3) [1]	getopt_long_only(GLIBC_2.3) [2]	lldiv(GLIBC_2.3) [1]	sethostname(GLIBC_2.3) [2]	wordexp(GLIBC_2.3) [1]
cuserid(GLIBC_2.3) [3]	getsubopt(GLIBC_2.3) [1]	longjmp(GLIBC_2.3) [1]	setlogmask(GLIBC_2.3) [1]	wordfree(GLIBC_2.3) [1]
daemon(GLIBC_2.3) [2]	gettimeofday(GLIBC_2.3) [1]	lrand48(GLIBC_2.3) [1]	setstate(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

[2]. this specification

[3]. SUSv2

An LSB conforming implementation shall provide the architecture specific data interfaces for Standard Library specified in Table 1-27, with the full functionality as described in the referenced underlying specification.

Table 1-27. libc - Standard Library Data Interfaces

__environ(GLIBC_2.3) [1]	_sys_errlist(GLIBC_2.3) [1]	getdate_err(GLIBC_2.3) [2]	opterr(GLIBC_2.3) [1]	optopt(GLIBC_2.3) [1]
_environ(GLIBC_2.3) [1]	environ(GLIBC_2.3) [2]	optarg(GLIBC_2.3) [2]	optind(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

Data Definitions for libc

This section defines global identifiers and their values that are associated with interfaces contained in libc. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content.

These definitions are intended to supplement those provided in the referenced underlying specifications.

This specification uses ISO/IEC 9899 C Language as the reference programming language, and data definitions are specified in ISO C format. The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

errno.h

#define EDEADLOCK	58

inttypes.h

typedef long intmax_t;
typedef unsigned long uintmax_t;
typedef unsigned long uintptr_t;
typedef unsigned long uint64_t;

limits.h

#define ULONG_MAX	0xFFFFFFFFFFFFFFFFUL
#define LONG_MAX	9223372036854775807L

#define CHAR_MIN	0
#define CHAR_MAX	255

setjmp.h

typedef long __jmp_buf[40];

signal.h

struct pt_regs
{
  unsigned long gpr[32];
  unsigned long nip;
  unsigned long msr;
  unsigned long orig_gpr3;
  unsigned long ctr;
  unsigned long link;
  unsigned long xer;
  unsigned long ccr;
  unsigned long softe;
  unsigned long trap;
  unsigned long dar;
  unsigned long dsisr;
  unsigned long result;
}
 ;

struct sigaction
{
  union
  {
    sighandler_t _sa_handler;
    void (*_sa_sigaction) (int, siginfo_t *, void *);
  }
  __sigaction_handler;
  sigset_t sa_mask;
  int sa_flags;
  void (*sa_restorer) (void);
}
 ;
#define MINSIGSTKSZ	2048
#define SIGSTKSZ	8192

struct sigcontext
{
  unsigned long _unused[4];
  int signal;
  unsigned long handler;
  unsigned long oldmask;
  struct pt_regs *regs;
  unsigned long gp_regs[48];
  double fp_regs[33];
}
 ;

stddef.h

typedef unsigned long size_t;
typedef long ptrdiff_t;

sys/ioctl.h

#define FIONREAD	1074030207
#define TIOCNOTTY	21538

sys/ipc.h

struct ipc_perm
{
  key_t __key;
  uid_t uid;
  gid_t gid;
  uid_t cuid;
  gid_t cgid;
  mode_t mode;
  unsigned int __seq;
  unsigned int __pad1;
  unsigned long __unused1;
  unsigned long __unused2;
}
 ;

sys/mman.h

#define MCL_FUTURE	16384
#define MCL_CURRENT	8192

sys/msg.h

typedef unsigned long msglen_t;
typedef unsigned long msgqnum_t;

struct msqid_ds
{
  struct ipc_perm msg_perm;
  time_t msg_stime;
  time_t msg_rtime;
  time_t msg_ctime;
  unsigned long __msg_cbytes;
  msgqnum_t msg_qnum;
  msglen_t msg_qbytes;
  pid_t msg_lspid;
  pid_t msg_lrpid;
  unsigned long __unused4;
  unsigned long __unused5;
}
 ;

sys/sem.h

struct semid_ds
{
  struct ipc_perm sem_perm;
  time_t sem_otime;
  time_t sem_ctime;
  unsigned long sem_nsems;
  unsigned long __unused3;
  unsigned long __unused4;
}
 ;

sys/shm.h

#define SHMLBA	(__getpagesize())

typedef unsigned long shmatt_t;

struct shmid_ds
{
  struct ipc_perm shm_perm;
  time_t shm_atime;
  time_t shm_dtime;
  time_t shm_ctime;
  size_t shm_segsz;
  pid_t shm_cpid;
  pid_t shm_lpid;
  shmatt_t shm_nattch;
  unsigned long __unused5;
  unsigned long __unused6;
}
 ;

sys/socket.h

typedef uint64_t __ss_aligntype;

sys/stat.h

#define _STAT_VER	1

struct stat
{
  dev_t st_dev;
  ino_t st_ino;
  nlink_t st_nlink;
  mode_t st_mode;
  uid_t st_uid;
  gid_t st_gid;
  int __pad2;
  dev_t st_rdev;
  off_t st_size;
  blksize_t st_blksize;
  blkcnt_t st_blocks;
  struct timespec st_atim;
  struct timespec st_mtim;
  struct timespec st_ctim;
  unsigned long __unused4;
  unsigned long __unused5;
  unsigned long __unused6;
}
 ;
struct stat64
{
  dev_t st_dev;
  ino64_t st_ino;
  nlink_t st_nlink;
  mode_t st_mode;
  uid_t st_uid;
  gid_t st_gid;
  int __pad2;
  dev_t st_rdev;
  off64_t st_size;
  blksize_t st_blksize;
  blkcnt64_t st_blocks;
  struct timespec st_atim;
  struct timespec st_mtim;
  struct timespec st_ctim;
  unsigned long __unused4;
  unsigned long __unused5;
  unsigned long __unused6;
}
 ;

sys/statvfs.h

struct statvfs
{
  unsigned long f_bsize;
  unsigned long f_frsize;
  fsblkcnt_t f_blocks;
  fsblkcnt_t f_bfree;
  fsblkcnt_t f_bavail;
  fsfilcnt_t f_files;
  fsfilcnt_t f_ffree;
  fsfilcnt_t f_favail;
  unsigned long f_fsid;
  unsigned long f_flag;
  unsigned long f_namemax;
  int __f_spare[6];
}
 ;
struct statvfs64
{
  unsigned long f_bsize;
  unsigned long f_frsize;
  fsblkcnt64_t f_blocks;
  fsblkcnt64_t f_bfree;
  fsblkcnt64_t f_bavail;
  fsfilcnt64_t f_files;
  fsfilcnt64_t f_ffree;
  fsfilcnt64_t f_favail;
  unsigned long f_fsid;
  unsigned long f_flag;
  unsigned long f_namemax;
  int __f_spare[6];
}
 ;

sys/types.h

typedef long int64_t;

typedef int64_t ssize_t;

termios.h

#define TAB1	1024
#define CR3	12288
#define CRDLY	12288
#define FF1	16384
#define FFDLY	16384
#define XCASE	16384
#define ONLCR	2
#define TAB2	2048
#define TAB3	3072
#define TABDLY	3072
#define BS1	32768
#define BSDLY	32768
#define OLCUC	4
#define CR1	4096
#define IUCLC	4096
#define VT1	65536
#define VTDLY	65536
#define NLDLY	768
#define CR2	8192

#define VWERASE	10
#define VREPRINT	11
#define VSUSP	12
#define VSTART	13
#define VSTOP	14
#define VDISCARD	16
#define VMIN	5
#define VEOL	6
#define VEOL2	8
#define VSWTC	9

#define IXOFF	1024
#define IXON	512

#define CSTOPB	1024
#define HUPCL	16384
#define CREAD	2048
#define CS6	256
#define CLOCAL	32768
#define PARENB	4096
#define CS7	512
#define VTIME	7
#define CS8	768
#define CSIZE	768
#define PARODD	8192

#define NOFLSH	0x80000000
#define ECHOKE	1
#define IEXTEN	1024
#define ISIG	128
#define ECHONL	16
#define ECHOE	2
#define ICANON	256
#define ECHOPRT	32
#define ECHOK	4
#define TOSTOP	4194304
#define PENDIN	536870912
#define ECHOCTL	64
#define FLUSHO	8388608

ucontext.h

#define NGREG	48

typedef struct sigcontext mcontext_t;

typedef struct ucontext
{
  unsigned long uc_flags;
  struct ucontext *uc_link;
  stack_t uc_stack;
  sigset_t uc_sigmask;
  mcontext_t uc_mcontext;
}
ucontext_t;

unistd.h

typedef long intptr_t;

utmp.h

struct lastlog
{
  int32_t ll_time;
  char ll_line[UT_LINESIZE];
  char ll_host[UT_HOSTSIZE];
}
 ;

struct utmp
{
  short ut_type;
  pid_t ut_pid;
  char ut_line[UT_LINESIZE];
  char ut_id[4];
  char ut_user[UT_NAMESIZE];
  char ut_host[UT_HOSTSIZE];
  struct exit_status ut_exit;
  int32_t ut_session;
  struct
  {
    int32_t tv_sec;
    int32_t tv_usec;
  }
  ut_tv;
  int32_t ut_addr_v6[4];
  char __unused[20];
}
 ;

utmpx.h

struct utmpx
{
  short ut_type;
  pid_t ut_pid;
  char ut_line[UT_LINESIZE];
  char ut_id[4];
  char ut_user[UT_NAMESIZE];
  char ut_host[UT_HOSTSIZE];
  struct exit_status ut_exit;
  int32_t ut_session;
  struct
  {
    int32_t tv_sec;
    int32_t tv_usec;
  }
  ut_tv;
  int32_t ut_addr_v6[4];
  char __unused[20];
}
 ;

Interfaces for libm

Table 1-28 defines the library name and shared object name for the libm library

Table 1-28. libm Definition

Library:	libm
SONAME:	libm.so.6

The behavior of the interfaces in this library is specified by the following specifications:

ISO C (1999)

SUSv2

ISO POSIX (2003)

Math

Interfaces for Math

An LSB conforming implementation shall provide the architecture specific functions for Math specified in Table 1-29, with the full functionality as described in the referenced underlying specification.

Table 1-29. libm - Math Function Interfaces

acos(GLIBC_2.3) [1]	cexp(GLIBC_2.3) [1]	expf(GLIBC_2.3) [1]	jnf(GLIBC_2.3) [2]	remquof(GLIBC_2.3) [1]
acosf(GLIBC_2.3) [1]	cexpf(GLIBC_2.3) [1]	expl(GLIBC_2.3) [1]	jnl(GLIBC_2.3) [2]	remquol(GLIBC_2.3) [1]
acosh(GLIBC_2.3) [1]	cexpl(GLIBC_2.3) [1]	expm1(GLIBC_2.3) [1]	ldexp(GLIBC_2.3) [1]	rint(GLIBC_2.3) [1]
acoshf(GLIBC_2.3) [1]	cimag(GLIBC_2.3) [1]	fabs(GLIBC_2.3) [1]	ldexpf(GLIBC_2.3) [1]	rintf(GLIBC_2.3) [1]
acoshl(GLIBC_2.3) [1]	cimagf(GLIBC_2.3) [1]	fabsf(GLIBC_2.3) [1]	ldexpl(GLIBC_2.3) [1]	rintl(GLIBC_2.3) [1]
acosl(GLIBC_2.3) [1]	cimagl(GLIBC_2.3) [1]	fabsl(GLIBC_2.3) [1]	lgamma(GLIBC_2.3) [1]	round(GLIBC_2.3) [1]
asin(GLIBC_2.3) [1]	clog(GLIBC_2.3) [1]	fdim(GLIBC_2.3) [1]	lgamma_r(GLIBC_2.3) [2]	roundf(GLIBC_2.3) [1]
asinf(GLIBC_2.3) [1]	clog10(GLIBC_2.3) [2]	fdimf(GLIBC_2.3) [1]	lgammaf(GLIBC_2.3) [1]	roundl(GLIBC_2.3) [1]
asinh(GLIBC_2.3) [1]	clog10f(GLIBC_2.3) [2]	fdiml(GLIBC_2.3) [1]	lgammaf_r(GLIBC_2.3) [2]	scalb(GLIBC_2.3) [1]
asinhf(GLIBC_2.3) [1]	clog10l(GLIBC_2.3) [2]	feclearexcept(GLIBC_2.3) [1]	lgammal(GLIBC_2.3) [1]	scalbf(GLIBC_2.3) [2]
asinhl(GLIBC_2.3) [1]	clogf(GLIBC_2.3) [1]	fegetenv(GLIBC_2.3) [1]	lgammal_r(GLIBC_2.3) [2]	scalbl(GLIBC_2.3) [2]
asinl(GLIBC_2.3) [1]	clogl(GLIBC_2.3) [1]	fegetexceptflag(GLIBC_2.3) [1]	llrint(GLIBC_2.3) [1]	scalbln(GLIBC_2.3) [1]
atan(GLIBC_2.3) [1]	conj(GLIBC_2.3) [1]	fegetround(GLIBC_2.3) [1]	llrintf(GLIBC_2.3) [1]	scalblnf(GLIBC_2.3) [1]
atan2(GLIBC_2.3) [1]	conjf(GLIBC_2.3) [1]	feholdexcept(GLIBC_2.3) [1]	llrintl(GLIBC_2.3) [1]	scalblnl(GLIBC_2.3) [1]
atan2f(GLIBC_2.3) [1]	conjl(GLIBC_2.3) [1]	feraiseexcept(GLIBC_2.3) [1]	llround(GLIBC_2.3) [1]	scalbn(GLIBC_2.3) [1]
atan2l(GLIBC_2.3) [1]	copysign(GLIBC_2.3) [1]	fesetenv(GLIBC_2.3) [1]	llroundf(GLIBC_2.3) [1]	scalbnf(GLIBC_2.3) [1]
atanf(GLIBC_2.3) [1]	copysignf(GLIBC_2.3) [1]	fesetexceptflag(GLIBC_2.3) [1]	llroundl(GLIBC_2.3) [1]	scalbnl(GLIBC_2.3) [1]
atanh(GLIBC_2.3) [1]	copysignl(GLIBC_2.3) [1]	fesetround(GLIBC_2.3) [1]	log(GLIBC_2.3) [1]	significand(GLIBC_2.3) [2]
atanhf(GLIBC_2.3) [1]	cos(GLIBC_2.3) [1]	fetestexcept(GLIBC_2.3) [1]	log10(GLIBC_2.3) [1]	significandf(GLIBC_2.3) [2]
atanhl(GLIBC_2.3) [1]	cosf(GLIBC_2.3) [1]	feupdateenv(GLIBC_2.3) [1]	log10f(GLIBC_2.3) [1]	significandl(GLIBC_2.3) [2]
atanl(GLIBC_2.3) [1]	cosh(GLIBC_2.3) [1]	finite(GLIBC_2.3) [3]	log10l(GLIBC_2.3) [1]	sin(GLIBC_2.3) [1]
cabs(GLIBC_2.3) [1]	coshf(GLIBC_2.3) [1]	finitef(GLIBC_2.3) [2]	log1p(GLIBC_2.3) [1]	sincos(GLIBC_2.3) [2]
cabsf(GLIBC_2.3) [1]	coshl(GLIBC_2.3) [1]	finitel(GLIBC_2.3) [2]	logb(GLIBC_2.3) [1]	sincosf(GLIBC_2.3) [2]
cabsl(GLIBC_2.3) [1]	cosl(GLIBC_2.3) [1]	floor(GLIBC_2.3) [1]	logf(GLIBC_2.3) [1]	sincosl(GLIBC_2.3) [2]
cacos(GLIBC_2.3) [1]	cpow(GLIBC_2.3) [1]	floorf(GLIBC_2.3) [1]	logl(GLIBC_2.3) [1]	sinf(GLIBC_2.3) [1]
cacosf(GLIBC_2.3) [1]	cpowf(GLIBC_2.3) [1]	floorl(GLIBC_2.3) [1]	lrint(GLIBC_2.3) [1]	sinh(GLIBC_2.3) [1]
cacosh(GLIBC_2.3) [1]	cpowl(GLIBC_2.3) [1]	fma(GLIBC_2.3) [1]	lrintf(GLIBC_2.3) [1]	sinhf(GLIBC_2.3) [1]
cacoshf(GLIBC_2.3) [1]	cproj(GLIBC_2.3) [1]	fmaf(GLIBC_2.3) [1]	lrintl(GLIBC_2.3) [1]	sinhl(GLIBC_2.3) [1]
cacoshl(GLIBC_2.3) [1]	cprojf(GLIBC_2.3) [1]	fmal(GLIBC_2.3) [1]	lround(GLIBC_2.3) [1]	sinl(GLIBC_2.3) [1]
cacosl(GLIBC_2.3) [1]	cprojl(GLIBC_2.3) [1]	fmax(GLIBC_2.3) [1]	lroundf(GLIBC_2.3) [1]	sqrt(GLIBC_2.3) [1]
carg(GLIBC_2.3) [1]	creal(GLIBC_2.3) [1]	fmaxf(GLIBC_2.3) [1]	lroundl(GLIBC_2.3) [1]	sqrtf(GLIBC_2.3) [1]
cargf(GLIBC_2.3) [1]	crealf(GLIBC_2.3) [1]	fmaxl(GLIBC_2.3) [1]	matherr(GLIBC_2.3) [2]	sqrtl(GLIBC_2.3) [1]
cargl(GLIBC_2.3) [1]	creall(GLIBC_2.3) [1]	fmin(GLIBC_2.3) [1]	modf(GLIBC_2.3) [1]	tan(GLIBC_2.3) [1]
casin(GLIBC_2.3) [1]	csin(GLIBC_2.3) [1]	fminf(GLIBC_2.3) [1]	modff(GLIBC_2.3) [1]	tanf(GLIBC_2.3) [1]
casinf(GLIBC_2.3) [1]	csinf(GLIBC_2.3) [1]	fminl(GLIBC_2.3) [1]	modfl(GLIBC_2.3) [1]	tanh(GLIBC_2.3) [1]
casinh(GLIBC_2.3) [1]	csinh(GLIBC_2.3) [1]	fmod(GLIBC_2.3) [1]	nan(GLIBC_2.3) [1]	tanhf(GLIBC_2.3) [1]
casinhf(GLIBC_2.3) [1]	csinhf(GLIBC_2.3) [1]	fmodf(GLIBC_2.3) [1]	nanf(GLIBC_2.3) [1]	tanhl(GLIBC_2.3) [1]
casinhl(GLIBC_2.3) [1]	csinhl(GLIBC_2.3) [1]	fmodl(GLIBC_2.3) [1]	nanl(GLIBC_2.3) [1]	tanl(GLIBC_2.3) [1]
casinl(GLIBC_2.3) [1]	csinl(GLIBC_2.3) [1]	frexp(GLIBC_2.3) [1]	nearbyint(GLIBC_2.3) [1]	tgamma(GLIBC_2.3) [1]
catan(GLIBC_2.3) [1]	csqrt(GLIBC_2.3) [1]	frexpf(GLIBC_2.3) [1]	nearbyintf(GLIBC_2.3) [1]	tgammaf(GLIBC_2.3) [1]
catanf(GLIBC_2.3) [1]	csqrtf(GLIBC_2.3) [1]	frexpl(GLIBC_2.3) [1]	nearbyintl(GLIBC_2.3) [1]	tgammal(GLIBC_2.3) [1]
catanh(GLIBC_2.3) [1]	csqrtl(GLIBC_2.3) [1]	gamma(GLIBC_2.3) [3]	nextafter(GLIBC_2.3) [1]	trunc(GLIBC_2.3) [1]
catanhf(GLIBC_2.3) [1]	ctan(GLIBC_2.3) [1]	gammaf(GLIBC_2.3) [2]	nextafterf(GLIBC_2.3) [1]	truncf(GLIBC_2.3) [1]
catanhl(GLIBC_2.3) [1]	ctanf(GLIBC_2.3) [1]	gammal(GLIBC_2.3) [2]	nextafterl(GLIBC_2.3) [1]	truncl(GLIBC_2.3) [1]
catanl(GLIBC_2.3) [1]	ctanh(GLIBC_2.3) [1]	hypot(GLIBC_2.3) [1]	nexttoward(GLIBC_2.3) [1]	y0(GLIBC_2.3) [1]
cbrt(GLIBC_2.3) [1]	ctanhf(GLIBC_2.3) [1]	hypotf(GLIBC_2.3) [1]	nexttowardf(GLIBC_2.3) [1]	y0f(GLIBC_2.3) [2]
cbrtf(GLIBC_2.3) [1]	ctanhl(GLIBC_2.3) [1]	hypotl(GLIBC_2.3) [1]	nexttowardl(GLIBC_2.3) [1]	y0l(GLIBC_2.3) [2]
cbrtl(GLIBC_2.3) [1]	ctanl(GLIBC_2.3) [1]	ilogb(GLIBC_2.3) [1]	pow(GLIBC_2.3) [1]	y1(GLIBC_2.3) [1]
ccos(GLIBC_2.3) [1]	dremf(GLIBC_2.3) [2]	ilogbf(GLIBC_2.3) [1]	pow10(GLIBC_2.3) [2]	y1f(GLIBC_2.3) [2]
ccosf(GLIBC_2.3) [1]	dreml(GLIBC_2.3) [2]	ilogbl(GLIBC_2.3) [1]	pow10f(GLIBC_2.3) [2]	y1l(GLIBC_2.3) [2]
ccosh(GLIBC_2.3) [1]	erf(GLIBC_2.3) [1]	j0(GLIBC_2.3) [1]	pow10l(GLIBC_2.3) [2]	yn(GLIBC_2.3) [1]
ccoshf(GLIBC_2.3) [1]	erfc(GLIBC_2.3) [1]	j0f(GLIBC_2.3) [2]	powf(GLIBC_2.3) [1]	ynf(GLIBC_2.3) [2]
ccoshl(GLIBC_2.3) [1]	erfcf(GLIBC_2.3) [1]	j0l(GLIBC_2.3) [2]	powl(GLIBC_2.3) [1]	ynl(GLIBC_2.3) [2]
ccosl(GLIBC_2.3) [1]	erfcl(GLIBC_2.3) [1]	j1(GLIBC_2.3) [1]	remainder(GLIBC_2.3) [1]
ceil(GLIBC_2.3) [1]	erff(GLIBC_2.3) [1]	j1f(GLIBC_2.3) [2]	remainderf(GLIBC_2.3) [1]
ceilf(GLIBC_2.3) [1]	erfl(GLIBC_2.3) [1]	j1l(GLIBC_2.3) [2]	remainderl(GLIBC_2.3) [1]
ceill(GLIBC_2.3) [1]	exp(GLIBC_2.3) [1]	jn(GLIBC_2.3) [1]	remquo(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

[2]. ISO C (1999)

[3]. SUSv2

An LSB conforming implementation shall provide the architecture specific data interfaces for Math specified in Table 1-30, with the full functionality as described in the referenced underlying specification.

Table 1-30. libm - Math Data Interfaces

signgam(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

Interfaces for libpthread

Table 1-31 defines the library name and shared object name for the libpthread library

Table 1-31. libpthread Definition

Library:	libpthread
SONAME:	libpthread.so.0

The behavior of the interfaces in this library is specified by the following specifications:

Large File Support

this specification

ISO POSIX (2003)

Realtime Threads

Interfaces for Realtime Threads

No external functions are defined for libpthread - Realtime Threads

Advanced Realtime Threads

Interfaces for Advanced Realtime Threads

No external functions are defined for libpthread - Advanced Realtime Threads

Posix Threads

Interfaces for Posix Threads

An LSB conforming implementation shall provide the architecture specific functions for Posix Threads specified in Table 1-32, with the full functionality as described in the referenced underlying specification.

Table 1-32. libpthread - Posix Threads Function Interfaces

_pthread_cleanup_pop(GLIBC_2.3) [1]	pthread_cancel(GLIBC_2.3) [2]	pthread_join(GLIBC_2.3) [2]	pthread_rwlock_destroy(GLIBC_2.3) [2]	pthread_setconcurrency(GLIBC_2.3) [2]
_pthread_cleanup_push(GLIBC_2.3) [1]	pthread_cond_broadcast(GLIBC_2.3.2) [2]	pthread_key_create(GLIBC_2.3) [2]	pthread_rwlock_init(GLIBC_2.3) [2]	pthread_setspecific(GLIBC_2.3) [2]
pread(GLIBC_2.3) [2]	pthread_cond_destroy(GLIBC_2.3.2) [2]	pthread_key_delete(GLIBC_2.3) [2]	pthread_rwlock_rdlock(GLIBC_2.3) [2]	pthread_sigmask(GLIBC_2.3) [2]
pread64(GLIBC_2.3) [3]	pthread_cond_init(GLIBC_2.3.2) [2]	pthread_kill(GLIBC_2.3) [2]	pthread_rwlock_timedrdlock(GLIBC_2.3) [2]	pthread_testcancel(GLIBC_2.3) [2]
pthread_attr_destroy(GLIBC_2.3) [2]	pthread_cond_signal(GLIBC_2.3.2) [2]	pthread_mutex_destroy(GLIBC_2.3) [2]	pthread_rwlock_timedwrlock(GLIBC_2.3) [2]	pwrite(GLIBC_2.3) [2]
pthread_attr_getdetachstate(GLIBC_2.3) [2]	pthread_cond_timedwait(GLIBC_2.3.2) [2]	pthread_mutex_init(GLIBC_2.3) [2]	pthread_rwlock_tryrdlock(GLIBC_2.3) [2]	pwrite64(GLIBC_2.3) [3]
pthread_attr_getguardsize(GLIBC_2.3) [2]	pthread_cond_wait(GLIBC_2.3.2) [2]	pthread_mutex_lock(GLIBC_2.3) [2]	pthread_rwlock_trywrlock(GLIBC_2.3) [2]	sem_close(GLIBC_2.3) [2]
pthread_attr_getschedparam(GLIBC_2.3) [2]	pthread_condattr_destroy(GLIBC_2.3) [2]	pthread_mutex_trylock(GLIBC_2.3) [2]	pthread_rwlock_unlock(GLIBC_2.3) [2]	sem_destroy(GLIBC_2.3) [2]
pthread_attr_getstackaddr(GLIBC_2.3) [2]	pthread_condattr_getpshared(GLIBC_2.3) [2]	pthread_mutex_unlock(GLIBC_2.3) [2]	pthread_rwlock_wrlock(GLIBC_2.3) [2]	sem_getvalue(GLIBC_2.3) [2]
pthread_attr_getstacksize(GLIBC_2.3) [2]	pthread_condattr_init(GLIBC_2.3) [2]	pthread_mutexattr_destroy(GLIBC_2.3) [2]	pthread_rwlockattr_destroy(GLIBC_2.3) [2]	sem_init(GLIBC_2.3) [2]
pthread_attr_init(GLIBC_2.3) [2]	pthread_condattr_setpshared(GLIBC_2.3) [2]	pthread_mutexattr_getpshared(GLIBC_2.3) [2]	pthread_rwlockattr_getpshared(GLIBC_2.3) [2]	sem_open(GLIBC_2.3) [2]
pthread_attr_setdetachstate(GLIBC_2.3) [2]	pthread_create(GLIBC_2.3) [2]	pthread_mutexattr_gettype(GLIBC_2.3) [2]	pthread_rwlockattr_init(GLIBC_2.3) [2]	sem_post(GLIBC_2.3) [2]
pthread_attr_setguardsize(GLIBC_2.3) [2]	pthread_detach(GLIBC_2.3) [2]	pthread_mutexattr_init(GLIBC_2.3) [2]	pthread_rwlockattr_setpshared(GLIBC_2.3) [2]	sem_timedwait(GLIBC_2.3) [2]
pthread_attr_setschedparam(GLIBC_2.3) [2]	pthread_equal(GLIBC_2.3) [2]	pthread_mutexattr_setpshared(GLIBC_2.3) [2]	pthread_self(GLIBC_2.3) [2]	sem_trywait(GLIBC_2.3) [2]
pthread_attr_setstackaddr(GLIBC_2.3) [2]	pthread_exit(GLIBC_2.3) [2]	pthread_mutexattr_settype(GLIBC_2.3) [2]	pthread_setcancelstate(GLIBC_2.3) [2]	sem_unlink(GLIBC_2.3) [2]
pthread_attr_setstacksize(GLIBC_2.3) [2]	pthread_getspecific(GLIBC_2.3) [2]	pthread_once(GLIBC_2.3) [2]	pthread_setcanceltype(GLIBC_2.3) [2]	sem_wait(GLIBC_2.3) [2]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

[3]. Large File Support

Interfaces for libgcc_s

Table 1-33 defines the library name and shared object name for the libgcc_s library

Table 1-33. libgcc_s Definition

Library:	libgcc_s
SONAME:	libgcc_s.so.1

The behavior of the interfaces in this library is specified by the following specifications:

this specification

Unwind Library

Interfaces for Unwind Library

An LSB conforming implementation shall provide the architecture specific functions for Unwind Library specified in Table 1-34, with the full functionality as described in the referenced underlying specification.

Table 1-34. libgcc_s - Unwind Library Function Interfaces

_Unwind_DeleteException(GCC_3.0) [1]	_Unwind_GetDataRelBase(GCC_3.0) [1]	_Unwind_GetLanguageSpecificData(GCC_3.0) [1]	_Unwind_RaiseException(GCC_3.0) [1]	_Unwind_SetIP(GCC_3.0) [1]
_Unwind_Find_FDE(GCC_3.0) [1]	_Unwind_GetGR(GCC_3.0) [1]	_Unwind_GetRegionStart(GCC_3.0) [1]	_Unwind_Resume(GCC_3.0) [1]
_Unwind_ForcedUnwind(GCC_3.0) [1]	_Unwind_GetIP(GCC_3.0) [1]	_Unwind_GetTextRelBase(GCC_3.0) [1]	_Unwind_SetGR(GCC_3.0) [1]

Referenced Specification(s)

[1]. this specification

Interface Definitions for libgcc_s

Table of Contents
_Unwind_DeleteException -- private C++ error handling method
_Unwind_Find_FDE -- private C++ error handling method
_Unwind_ForcedUnwind -- private C++ error handling method
_Unwind_GetDataRelBase -- private IA64 C++ error handling method
_Unwind_GetGR -- private C++ error handling method
_Unwind_GetIP -- private C++ error handling method
_Unwind_GetLanguageSpecificData -- private C++ error handling method
_Unwind_GetRegionStart -- private C++ error handling method
_Unwind_GetTextRelBase -- private IA64 C++ error handling method
_Unwind_RaiseException -- private C++ error handling method
_Unwind_Resume -- private C++ error handling method
_Unwind_SetGR -- private C++ error handling method
_Unwind_SetIP -- private C++ error handling method

Description

_Unwind_ForcedUnwind raises an exception for forced unwinding, passing along the given exception object, which should have its exception_class and exception_cleanup fields set. The exception object has been allocated by the language-specific runtime, and has a language-specific format, except that it shall contain an _Unwind_Exception struct.

Forced unwinding is a single-phase process. stop and stop_parameter control the termination of the unwind process instead of the usual personality routine query. stop is called for each unwind frame, with the parameteres described for the usual personality routine below, plus an additional stop_parameter.

Return Value

When stop identifies the destination frame, it transfers control to the user code as appropriate without returning, normally after calling _Unwind_DeleteException. If not, then it should return an _Unwind_Reason_Code value.

If stop returns any reason code other than _URC_NO_REASON, then the stack state is indeterminate from the point of view of the caller of _Unwind_ForcedUnwind. Rather than attempt to return, therefore, the unwind library should use the exception_cleanup entry in the exception, and then call abort.

_URC_NO_REASON: This is not the destination from. The unwind runtime will call frame's personality routine with the _UA_FORCE_UNWIND and _UA_CLEANUP_PHASE flag set in actions, and then unwind to the next frame and call the stop function again.
_URC_END_OF_STACK: In order to allow _Unwind_ForcedUnwind to perform special processing when it reaches the end of the stack, the unwind runtime will call it after the last frame is rejected, with a NULL stack pointer in the context, and the stop function shall catch this condition. It may return this code if it cannot handle end-of-stack.
_URC_FATAL_PHASE2_ERROR: The stop function may return this code for other fatal conditions like stack corruption.

_Unwind_GetDataRelBase

Name

_Unwind_GetDataRelBase -- private IA64 C++ error handling method

Synopsis

_Unwind_Ptr _Unwind_GetDataRelBase((struct _Unwind_Context *context));

Description

_Unwind_GetDataRelBase returns the global pointer in register one for context.

_Unwind_GetGR

Name

_Unwind_GetGR -- private C++ error handling method

Synopsis

_Unwind_Word _Unwind_GetGR((struct _Unwind_Context *context), int index);

Description

Description

_Unwind_RaiseException raises an exception, passing along the given exception object, which should have its exception_class and exception_cleanup fields set. The exception object has been allocated by the language-specific runtime, and has a language-specific format, exception that it shall contain an _Unwind_Exception.

Return Value

_Unwind_RaiseException does not return unless an error condition is found. If an error condition occurs, an _Unwind_Reason_Code is returnd:

_URC_END_OF_STACK: The unwinder encountered the end of the stack during phase one without finding a handler. The unwind runtime will not have modified the stack. The C++ runtime will normally call uncaught_exception in this case.
_URC_FATAL_PHASE1_ERROR: The unwinder encountered an unexpected error during phase one, because of something like stack corruption. The unwind runtime will not have modified the stack. The C++ runtime will normally call terminate in this case.
_URC_FATAL_PHASE2_ERROR: The unwinder encountered an unexpected error during phase two. This is usually a throw, which will call terminate.

Interfaces for libdl

Table 1-35 defines the library name and shared object name for the libdl library

Table 1-35. libdl Definition

Library:	libdl
SONAME:	libdl.so.2

The behavior of the interfaces in this library is specified by the following specifications:

this specification

ISO POSIX (2003)

Dynamic Loader

Interfaces for Dynamic Loader

An LSB conforming implementation shall provide the architecture specific functions for Dynamic Loader specified in Table 1-36, with the full functionality as described in the referenced underlying specification.

Table 1-36. libdl - Dynamic Loader Function Interfaces

dladdr(GLIBC_2.3) [1]

dlclose(GLIBC_2.3) [2]

dlerror(GLIBC_2.3) [2]

dlopen(GLIBC_2.3) [1]

dlsym(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. this specification

[2]. ISO POSIX (2003)

Interfaces for libcrypt

Table 1-37 defines the library name and shared object name for the libcrypt library

Table 1-37. libcrypt Definition

Library:	libcrypt
SONAME:	libcrypt.so.1

The behavior of the interfaces in this library is specified by the following specifications:

ISO POSIX (2003)

Encryption

Interfaces for Encryption

An LSB conforming implementation shall provide the architecture specific functions for Encryption specified in Table 1-38, with the full functionality as described in the referenced underlying specification.

Table 1-38. libcrypt - Encryption Function Interfaces

crypt(GLIBC_2.3) [1]

encrypt(GLIBC_2.3) [1]

setkey(GLIBC_2.3) [1]

Referenced Specification(s)

[1]. ISO POSIX (2003)

II. Utility Libraries

Table of Contents
2. Libraries

Chapter 2. Libraries

The Utility libraries are those that are commonly used, but not part of the Single Unix Specification.

Interfaces for libz

Table 2-1. libz Definition

Library:	libz
SONAME:	libz.so.1

Compression Library

Interfaces for Compression Library

Data Definitions for libz

This section contains standard data definitions that describe system data. These definitions are organized into groups that correspond to system headers. This convention is used as a convenience for the reader, and does not imply the existence of these headers, or their content.

ISO C serves as the LSB reference programming language, and data definitions are specified in ISO C . The C language is used here as a convenient notation. Using a C language description of these data objects does not preclude their use by other programming languages.

Interfaces for libncurses

Table 2-2. libncurses Definition

Library:	libncurses
SONAME:	libncurses.so.5

Curses

Interfaces for Curses

Data Definitions for libncurses

curses.h















typedef int bool;

Interfaces for libutil

Table 2-3. libutil Definition

Library:	libutil
SONAME:	libutil.so.1

The behavior of the interfaces in this library is specified by the following standards.

Linux Standard Base[1]

Utility Functions

Interfaces for Utility Functions

Table 2-4. libutil - Utility Functions Function Interfaces

forkpty(GLIBC_2.3)[1]	login_tty(GLIBC_2.3)[1]	logwtmp(GLIBC_2.3)[1]
login(GLIBC_2.3)[1]	logout(GLIBC_2.3)[1]	openpty(GLIBC_2.3)[1]

Appendix A. Alphabetical Listing of Interfaces

libgcc_s

The behaviour of the interfaces in this library is specified by the following Standards.

this specification

Table A-1. libgcc_s Function Interfaces

_Unwind_DeleteException[1]	_Unwind_GetIP[1]	_Unwind_Resume[1]
_Unwind_Find_FDE[1]	_Unwind_GetLanguageSpecificData[1]	_Unwind_SetGR[1]
_Unwind_ForcedUnwind[1]	_Unwind_GetRegionStart[1]	_Unwind_SetIP[1]
_Unwind_GetDataRelBase[1]	_Unwind_GetTextRelBase[1]
_Unwind_GetGR[1]	_Unwind_RaiseException[1]

Linux Packaging Specification

Table of Contents

I. Package Format and Installation

1. Software Installation

Package Dependencies
Package Architecture Considerations

I. Package Format and Installation

Table of Contents
1. Software Installation

Chapter 1. Software Installation

Package Dependencies

The LSB runtime environment shall provde the following dependencies.

lsb-core-ppc64: This dependency is used to indicate that the application is dependent on features contained in the LSB-Core specification.

Other LSB modules may add additional dependencies; such dependencies shall have the format lsb-module-ppc64.

Package Architecture Considerations

All packages must specify an architecture of ppc64. A LSB runtime environment must accept an architecture of ppc64 even if the native architecture is different.

The archnum value in the Lead Section shall be 0x0010.

Free Documentation License

Table of Contents

A. GNU Free Documentation License

PREAMBLE
APPLICABILITY AND DEFINITIONS
VERBATIM COPYING
COPYING IN QUANTITY
MODIFICATIONS
COMBINING DOCUMENTS
COLLECTIONS OF DOCUMENTS
AGGREGATION WITH INDEPENDENT WORKS
TRANSLATION
TERMINATION
FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents

Appendix A. GNU Free Documentation License

Version 1.1, March 2000

Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

PREAMBLE

The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you".

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

COPYING IN QUANTITY

If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five).
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
In any section entitled "Acknowledgements" or "Dedications", preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version.
Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements."

COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.

TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.

TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. A copy of the license is included in the section entitled "GNU Free Documentation License".

If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.