> Yeah, this is normal, well... at least it happens on all > OS 10.1.x based systems. When 'gcc' switches to "old" cpp, it > correctly handles the file.
CFLAGS with
--traditional-cpp
added force this directly. I.e. it wont try smart mode first.
DW
