Making GCC complain about chained includes

Dear Lazyweb,

When you have an include file that includes a second one and use a function that exists on the second, you won’t get a warning, because you’ll have the function defined. The problem appears only when you think you can remove the second include (or maybe because it didn’t have the object/functions you’ll need).

So, the question is: there is a way to make GCC (or more directly, gpp[1]) complain about functions not declared directly on included headers?

[1] The GNU Pre-Processor.