> On Tue, Jul 17, 2001 at 07:55:18PM +0100, David Malone wrote:
> > I suspect that this is my fault for not doing a buildworld after
> > turning on WARNS stuff in inetd.

> YES!  Why are you committing these "very easy to break the build, as
> we've seen" changes w/o full `make buildworld' testing?!?

I should have been more careful, but I actually tested the change
on the i386 and alpha and checked that it didn't produce any code
changes. Unfortunately, gcc has an undocumented feature of ignoring
some warnings in system C header files. (Maybe this feature has
been there for years, but the fact that gcc gives out about system
header files is something that's caused problems for me before.)

I would have thought that any file included with

#include <...>

would count as a system header file, but it seems gcc has some
other criteron for deciding. I've managed to trace it back to cpp
writing out lines like:

# 1 "/usr/include/tcpd.h" 1 3

where the "3" at the end seems to mean a system header file. And
in tradcpp.c it seems to set a varible system_header_p if the
include is a <...> as opposed to a "...", but I haven't found out
where the "3" comes from yet.

Ahh - I'm looking at the wrong gcc sources. The 2.95.3 sources
(which uses the old gcc cpp) decides if something is a system
include based on examining a list which doesn't seem to get
initialised if you say "-nostdinc". The newer gcc sources (2.96.20000711
with the new cpp) seem to do the <...> vs. "..." thing.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to