William Fulton writes: > > Have you tried "CC -E runme.cxx"? > > > > > Indeed and that works, but ccache doesn't attempt to tweak the compiler > options to suite. The problem is the interpretation of -c is slightly > different with gcc, which is basically saying don't link, whereas CC > seems to expect that -c will generate a binary output and so warns when > asked to generate preprocessor output. ccache works well with gcc > (amongst other compilers) and clearly is not used much with CC. It's > looking like a change to ccache is needed to deal with this slightly > different behaviour of the workshop compilers in order to get the full > efficiencies of cacheing.
Every compiler is a bit different ... but this looks like the kind of case where you could file an RFE and get something changed. The two arguments of "gcc does it this way so it's a barrier to interoperability" and "the warning doesn't actually help anyone do anything" would probably be effective. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677