Kevin Ryde | 4 Jan 2004 00:39
Picon
Picon

Re: doc cc -c -o

Peter Eisentraut <peter_e <at> gmx.net> writes:
>
> AC_PROG_CC_C_O is pretty unsuitable for this.  It only defines a
> preprocessor macro, nothing that you can use in a makefile.

Ah yes (for some reason I thought NO_MINUS_C_MINUS_O was a shell
variable rather than an AC_DEFINE).  New effort then, without
bothering about the cross reference,

        * doc/autoconf.texi (Limitations of Usual Tools): Note cc may not
        allow -c -o together.

     `cc -c foo.c' produces a `foo.o' object file.  Most compilers
     allow a `-o' option to direct the output to a different file, but
     POSIX doesn't require this (with `-c') so it should be avoided.

--- autoconf.texi.~1.785.~	2004-01-04 06:54:32.000000000 +1000
+++ autoconf.texi	2004-01-04 09:37:03.000000000 +1000
 <at>  <at>  -10847,6 +10847,10  <at>  <at> 
 assemble.   <at> samp{cc -c foo.S} will appear to succeed, but in fact does
 nothing.

+ <at> samp{cc -c foo.c} produces a  <at> file{foo.o} object file.  Most compilers
+allow a  <at> samp{-o} option to direct the output to a different file, but
+POSIX doesn't require this (with  <at> samp{-c}) so it should be avoided.
+
 The default executable, produced by  <at> samp{cc foo.c}, can be

  <at> itemize

Gmane