On 05/20/2011 03:32 PM, Reuben Thomas wrote:
> I've just been playing with flymake. To make it work at all I copied
> the following rule into my src/Makefile.am from the flymake manual:
>
> check-syntax:
> gcc -o nul -S ${CHK_SOURCES}> > Secondly, the -o nul option to gcc seems to be an > undocumented-but-widely-used trick to get gcc not to output the > results of the compilation. Any observations on this before I write a > bug report suggesting it be documented? (Generally I find writing gcc > and glibc bug reports without help a waste of time (above my pay > grade, as it were).) nul does not work anywhere besides Windows; elsewhere it is spelled /dev/null. This is a fundamental manner of how the null device works (once you spell its name correctly). That is, pretty much all compilers should support '-o /dev/null' as a way to suppress an object file, so I don't think this is an undocumented gcc feature. As for the rest of your questions, I'm not familiar enough with flymake to give a good answer. -- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
