logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

strip.1p (4819B)


  1. '\" et
  2. .TH STRIP "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. strip
  12. \(em remove unnecessary information from strippable files
  13. (\fBDEVELOPMENT\fP)
  14. .SH SYNOPSIS
  15. .LP
  16. .nf
  17. strip \fIfile\fR...
  18. .fi
  19. .SH DESCRIPTION
  20. A strippable file is defined as a relocatable, object, or executable
  21. file.
  22. On XSI-conformant systems, a strippable file can also be an archive
  23. of object or relocatable files.
  24. .P
  25. The
  26. .IR strip
  27. utility shall remove from strippable files named by the
  28. .IR file
  29. operands any information the implementor deems unnecessary for
  30. execution of those files. The nature of that information is
  31. unspecified. The effect of
  32. .IR strip
  33. on object and executable files shall be similar to the use of the
  34. .BR \-s
  35. option to
  36. .IR c99
  37. or
  38. .IR fort77 .
  39. The effect of
  40. .IR strip
  41. on an archive of object files shall be similar to the use of the
  42. .BR \-s
  43. option to
  44. .IR c99
  45. or
  46. .IR fort77
  47. for each object file in the archive.
  48. .SH OPTIONS
  49. None.
  50. .SH OPERANDS
  51. The following operand shall be supported:
  52. .IP "\fIfile\fR" 10
  53. A pathname referring to a strippable file.
  54. .SH STDIN
  55. Not used.
  56. .SH "INPUT FILES"
  57. The input files shall be in the form of strippable files successfully
  58. produced by any compiler defined by this volume of POSIX.1\(hy2017
  59. or produced by creating or updating an archive of such files
  60. using the
  61. .IR ar
  62. utility.
  63. .SH "ENVIRONMENT VARIABLES"
  64. The following environment variables shall affect the execution of
  65. .IR strip :
  66. .IP "\fILANG\fP" 10
  67. Provide a default value for the internationalization variables that are
  68. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  69. .IR "Section 8.2" ", " "Internationalization Variables"
  70. for the precedence of internationalization variables used to determine
  71. the values of locale categories.)
  72. .IP "\fILC_ALL\fP" 10
  73. If set to a non-empty string value, override the values of all the
  74. other internationalization variables.
  75. .IP "\fILC_CTYPE\fP" 10
  76. Determine the locale for the interpretation of sequences of bytes of
  77. text data as characters (for example, single-byte as opposed to
  78. multi-byte characters in arguments).
  79. .IP "\fILC_MESSAGES\fP" 10
  80. .br
  81. Determine the locale that should be used to affect the format and
  82. contents of diagnostic messages written to standard error.
  83. .IP "\fINLSPATH\fP" 10
  84. Determine the location of message catalogs for the processing of
  85. .IR LC_MESSAGES .
  86. .SH "ASYNCHRONOUS EVENTS"
  87. Default.
  88. .SH STDOUT
  89. Not used.
  90. .SH STDERR
  91. The standard error shall be used only for diagnostic messages.
  92. .SH "OUTPUT FILES"
  93. The
  94. .IR strip
  95. utility shall produce strippable files of unspecified format.
  96. .SH "EXTENDED DESCRIPTION"
  97. None.
  98. .SH "EXIT STATUS"
  99. The following exit values shall be returned:
  100. .IP "\00" 6
  101. Successful completion.
  102. .IP >0 6
  103. An error occurred.
  104. .SH "CONSEQUENCES OF ERRORS"
  105. Default.
  106. .LP
  107. .IR "The following sections are informative."
  108. .SH "APPLICATION USAGE"
  109. None.
  110. .SH EXAMPLES
  111. None.
  112. .SH RATIONALE
  113. Historically, this utility has been used to remove the symbol table
  114. from a strippable file. It was included since it is known that the
  115. amount of symbolic information can amount to several megabytes; the
  116. ability to remove it in a portable manner was deemed important,
  117. especially for smaller systems.
  118. .P
  119. The behavior of
  120. .IR strip
  121. on object and executable files is said to be the same as the
  122. .BR \-s
  123. option to a compiler. While the end result is essentially the same,
  124. it is not required to be identical.
  125. .P
  126. XSI-conformant systems support use of
  127. .IR strip
  128. on archive files containing object files or relocatable files.
  129. .SH "FUTURE DIRECTIONS"
  130. None.
  131. .SH "SEE ALSO"
  132. .IR "\fIar\fR\^",
  133. .IR "\fIc99\fR\^",
  134. .IR "\fIfort77\fR\^"
  135. .P
  136. The Base Definitions volume of POSIX.1\(hy2017,
  137. .IR "Chapter 8" ", " "Environment Variables"
  138. .\"
  139. .SH COPYRIGHT
  140. Portions of this text are reprinted and reproduced in electronic form
  141. from IEEE Std 1003.1-2017, Standard for Information Technology
  142. -- Portable Operating System Interface (POSIX), The Open Group Base
  143. Specifications Issue 7, 2018 Edition,
  144. Copyright (C) 2018 by the Institute of
  145. Electrical and Electronics Engineers, Inc and The Open Group.
  146. In the event of any discrepancy between this version and the original IEEE and
  147. The Open Group Standard, the original IEEE and The Open Group Standard
  148. is the referee document. The original Standard can be obtained online at
  149. http://www.opengroup.org/unix/online.html .
  150. .PP
  151. Any typographical or formatting errors that appear
  152. in this page are most likely
  153. to have been introduced during the conversion of the source files to
  154. man page format. To report such errors, see
  155. https://www.kernel.org/doc/man-pages/reporting_bugs.html .