afcc.1 2.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136
  1. .TH AFCC 1
  2. .SH NAME
  3. afcc \- fast ACK compatible ANSI C compiler
  4. .SH SYNOPSIS
  5. .B afcc
  6. [
  7. .B \-c
  8. ]
  9. [
  10. .B \-v
  11. ]
  12. [
  13. .B \-vn
  14. ]
  15. [ \fB\-D\fIname\fR ]
  16. [ \fB\-D\fIname\fB=\fIdef\fR ]
  17. [
  18. .BI \-I pathname
  19. ]
  20. [
  21. .B \-w
  22. ]
  23. [
  24. .B \-o
  25. .I outfile
  26. ]
  27. [
  28. .BI \-U name
  29. ]
  30. [
  31. .BI -M compiler
  32. ]
  33. .I sourcefile ...
  34. .SH DESCRIPTION
  35. .LP
  36. .I Afcc
  37. is a fast
  38. .B C
  39. compiler. It translates
  40. .B C
  41. programs
  42. into ack(1)-compatible relocatable object modules, and does so in one pass.
  43. Then, if the \fB\-c\fP flag is not given,
  44. .I afcc
  45. offers the object modules to a link-editor,
  46. to create an executable binary.
  47. .LP
  48. .I Afcc
  49. accepts several types of filename arguments. Files with
  50. names ending in
  51. .B .c
  52. are taken to be
  53. .B C
  54. source programs.
  55. They are compiled, and the resulting object module is placed in the current
  56. directory.
  57. The object module is named after its source file, the suffix
  58. .B .o
  59. replacing
  60. .BR .c
  61. in the name of the object.
  62. .LP
  63. Other arguments refer to loader options,
  64. object modules, or object libraries.
  65. Unless the
  66. .B \-c
  67. flag is given, these modules and libraries, together with the results of any
  68. specified compilations, are passed (in the order given) to the
  69. link-editor to produce
  70. an output file named
  71. .IR a.out .
  72. You can specify a name for the executable by using the
  73. .B \-o
  74. option.
  75. .SH OPTIONS
  76. .LP
  77. .IP \fB\-c\fP
  78. .br
  79. Suppress the loading phase of the compilation, and force an object module to
  80. be produced, even if only one program is compiled.
  81. A single object module can be named explicitly using the
  82. .B \-o
  83. option.
  84. .IP \fB\-D\fIname\fR\fB=\fIdef\fR
  85. Define a symbol
  86. .I name
  87. to the
  88. preprocessor, as if by "#define".
  89. .IP \fB\-D\fIname\fR
  90. .br
  91. same as \fB\-D\fIname\fB=1\fR.
  92. .IP \fB\-I\fIpathname\fR
  93. .br
  94. Add
  95. .I pathname
  96. to the list of directories in which to search for
  97. .B #include
  98. files with filenames not beginning with slash.
  99. The compiler first searches for
  100. .B #include
  101. files in the directory containing
  102. .I sourcefile,
  103. then in directories in
  104. .B \-I
  105. options, then in the ACK include directory,
  106. and finally, in
  107. .I /usr/include.
  108. .IP "\fB\-o \fIoutput\fR"
  109. Name the final output file
  110. .I output.
  111. .IP \fB\-U\fIname\fR
  112. .br
  113. Remove any initial definition of
  114. .I name.
  115. .IP \fB\-v\fP
  116. .br
  117. Verbose. Print the commands as they are executed.
  118. .IP \fB\-vn\fP
  119. .br
  120. Verbose, no execute. Only print the commands, do not execute them.
  121. .IP \fB\-w\fP
  122. suppress warning messages.
  123. .IP \fB\-M\fIcompiler\fR
  124. .br
  125. use \fIcompiler\fR as C compiler instead of the default.
  126. .LP
  127. Object modules produced by ack(1) and
  128. .I afcc
  129. can be freely mixed.
  130. .SH "SEE ALSO"
  131. .IP [1]
  132. B.W. Kernighan, D. Ritchie, "\fIThe C programming Language\fP", Prentice-Hall Inc., 1978
  133. .IP [2]
  134. ack(1) manual page.
  135. .SH DIAGNOSTICS
  136. Diagnostics are intended to be self-explanatory.