Interpretations

Answering questions that may arise related to the meaning of portions of an IEEE standard concerning specific applications.

IEEE Standards Interpretation for IEEE Std 1003.1™-2001 IEEE Standard Standard for Information Technology -- Portable Operating System Interface (POSIX®)

Copyright © 2006 by the Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue New York, New York 10016-5997 USA All Rights Reserved.

Interpretations are issued to explain and clarify the intent of a standard and do not constitute an alteration to the original standard. In addition, interpretations are not intended to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standards Department for the appropriate license. Use of the information contained in this document is at your own risk.

IEEE Standards Department Copyrights and Permissions 445 Hoes Lane, Piscataway, New Jersey 08855-1331, USA

Interpretation Request #103
Topic: strip object files, archives, executables Relevant Sections: XCU strip

Edition of Specification (Year): 2004

Defect code : 2. Omission

The ar description of the -s option states that "This option is useful to restore the archive symbol table after it has been stripped; see strip." The strip operands section states that its operand is "A pathname refering to an executable file." and makes no references to archives.

Make it clear that strip is applicable to object files and archives, eliminates all information unnecessary for linking for individual object files and the object files contained within an archive and eliminates the archive symbol table.

Interpretation Response
The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.

Rationale for Interpretation
This was considered as two issues:the first was that the term "executable" should also include relocatable and object files. The second issue was the contradiction between ar and strip.