LSB Core - Generic 5.0 3 Requirements
• The implementation shall be capable of executing compiled applications having the
format and using the system interfaces described in this specification.
• The implementation shall provide libraries containing the interfaces specified by this
specification, and shall provide a dynamic linking mechanism that allows these inter-
faces to be attached to applications at runtime. All the interfaces shall behave as spe-
cified in this specification.
• The map of virtual memory provided by the implementation shall conform to the re-
quirements of this specification.
• 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
specification.
• The implementation shall provide all of the mandatory interfaces in their entirety.
• The implementation may provide one or more of the optional interfaces. Each op-
tional interface that is provided shall be provided in its entirety. The product docu-
mentation shall state which optional interfaces are provided.
• The implementation shall provide all files and utilities specified as part of this spe-
cification in the format defined here and in other documents normatively included by
reference. All commands and utilities shall behave as required by this specification.
The implementation shall also provide all mandatory components of an application's
runtime environment that are included or referenced in this specification.
• 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 imple-
mentation might sell the hardware, operating system, and windowing system as separ-
ately 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.
3.3 LSB Application Conformance
A conforming application containing object files is necessarily architecture specific, and
must conform to both the generic LSB Core specification (LSB Core - Generic) and the
relevant architecture specific part of the LSB Core Specification. A conforming applica-
tion which contains no object files may be architecture neutral. Architecture neutral ap-
plications shall conform only to the requirements of the generic LSB Core specification
(LSB Core - Generic).
A conforming application shall satisfy the following requirements:
• Executable files shall be either object files in the format defined in the Object Format
section of this specification, or script files in a scripting language where the
interpreter is required by this specification.
• Object files shall participate in dynamic linking as defined in the Program Loading
and Linking section of this specification.
• Object files shall employ only the instructions, traps, and other low-level facilities
defined as being for use by applications in the Low-Level System Information section
of this specification
• If the application requires any optional interface defined in this specification in order
to be installed or to execute successfully, the requirement for that optional interface
shall be stated in the application's documentation.
• The application shall not use any interface or data format that is not required to be
provided by a conforming implementation, unless such an interface or data format is
supplied by another application through direct invocation of that application during
© 2015 Linux Foundation 17