From owner-freebsd-current Wed Apr 17 20:27:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA09190 for current-outgoing; Wed, 17 Apr 1996 20:27:12 -0700 (PDT) Received: from lear35.cytex.com (root@lear35.cytex.com [38.252.97.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA09184 for ; Wed, 17 Apr 1996 20:27:08 -0700 (PDT) Received: (from mbartley@localhost) by lear35.cytex.com (8.7.5/8.7.3) id UAA02026 for freebsd-current@freebsd.org; Wed, 17 Apr 1996 20:27:06 -0700 (PDT) From: Matt Bartley Message-Id: <199604180327.UAA02026@lear35.cytex.com> Subject: netinet/in_proto.c warnings To: freebsd-current@freebsd.org Date: Wed, 17 Apr 1996 20:27:05 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While compiling the -current kernel (last sup from sup2 at 1996/04/18 01:54 UTC) I get the following warning messages. I think this has been happening for a long time; I just thought I'd stop ignoring it. (reformatted to < 80 character line lengths) cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -nostdinc -I. -I../.. -I../../sys -I../../../include -DI586_CPU -DEXT2FS -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../netinet/in_proto.c ../../netinet/in_proto.c:96: warning: initialization from incompatible pointer type ../../netinet/in_proto.c:112: warning: initialization from incompatible pointer type ../../netinet/in_proto.c:117: warning: initialization from incompatible pointer type ../../netinet/in_proto.c:121: warning: initialization from incompatible pointer type ../../netinet/in_proto.c:126: warning: initialization from incompatible pointer type ../../netinet/in_proto.c:131: warning: initialization from incompatible pointer type ../../netinet/in_proto.c:166: warning: initialization from incompatible pointer type It then goes on to compile the kernel with no apparent harm done. Should I go back to ignoring it? I couldn't find any mention of this in the list archive. md5 /usr/src/sys/netinet/in_proto.c MD5 (/usr/src/sys/netinet/in_proto.c) = 504c74a82d6596a537bc25492d8eb4f0 ls -l /usr/src/sys/netinet/in_proto.c -rw-rw-r-- 1 root bin 6534 Mar 26 13:49 /usr/src/sys/netinet/in_proto.c