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
On Wed, 18 Jul 2001, David Malone wrote:
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
Am I the only one who sees this ?
=== usr.sbin/inetd
cc -nostdinc -O -pipe -DINET6 -DIPSEC -DLOGIN_CAP
-I/usr/obj/flat/src/i386/usr/include -W -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wpoin
ter-arith -Wno-uninitialized -Werror -Wreturn-type -Wcast-qual -Wwrite-strings
-Wswitch
On Tue, Jul 17, 2001 at 08:38:13PM +0200, Poul-Henning Kamp wrote:
Am I the only one who sees this ?
I suspect that this is my fault for not doing a buildworld after
turning on WARNS stuff in inetd. I think the problem must be that
-nostdinc must cause errors to be issued for files which
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'll
