From owner-freebsd-current Wed Jan 27 14:58:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25749 for freebsd-current-outgoing; Wed, 27 Jan 1999 14:58:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25742 for ; Wed, 27 Jan 1999 14:58:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id OAA67227; Wed, 27 Jan 1999 14:58:21 -0800 (PST) (envelope-from dillon) Date: Wed, 27 Jan 1999 14:58:21 -0800 (PST) From: Matthew Dillon Message-Id: <199901272258.OAA67227@apollo.backplane.com> To: current@FreeBSD.ORG Subject: -Wall, -Wcast-qual has been turned on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -Wall and -Wcast-qual has been turned on in /usr/src/share/mk/bsd.kern.mk. Please note that you will see a lot of warnings ( but no fatal errors ) while compiling the kernel now until we can get it all cleaned up. I am working a first-pass cleanup now. Do not 'cleanup' the code unless you know what you are doing, there are some odd things in there that are being caught now. Specifically, nobody should clean up the enumeration warnings or the &&/|| warnings unless they know exactly what they are doing. The volatile warnings also need esspecial attention. If you are not familiar with how volatile is used with memory-mapped I/O, do not try to clean these up. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message