On 5/16/05, John Hasler <[EMAIL PROTECTED]> wrote:
> It may not have to do with the compiler. The build system may be using cpp
> for some purpose of it's own. Preprocessing source for the C compiler is
> not the only thing cpp gets used for.
That might be true, but two points:
1) quoting from the GNU cpp man page
The C preprocessor is intended to be used only with C, C++, and Objec-
tive-C source code. In the past, it has been abused as a general text
processor. It will choke on input which does not obey C's lexical
rules. For example, apostrophes will be interpreted as the beginning
of character constants, and cause errors. Also, you cannot rely on it
preserving characteristics of the input which are not significant to
C-family languages. If a Makefile is preprocessed, all the hard tabs
will be removed, and the Makefile will not work.
2) The "safe" way to call cpp is to use "gcc -E" (or an equivalent),
so that the "correct" version gets called and search paths are set to
reasonable values.
--
Michael A. Marsh
http://www.umiacs.umd.edu/~mmarsh
http://mamarsh.blogspot.com
