From owner-freebsd-current Sat Jan 29 20: 1:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id DA690158EE; Sat, 29 Jan 2000 20:01:10 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id NAA04949; Sun, 30 Jan 2000 13:00:58 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id NAA20209; Sun, 30 Jan 2000 13:00:57 +0900 (JST) Received: from localhost ([192.168.245.194]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id NAA20319; Sun, 30 Jan 2000 13:00:56 +0900 (JST) To: bloom@acm.org Cc: kris@hub.freebsd.org, current@FreeBSD.ORG Subject: Re: kernel breakage from ipfw6? In-Reply-To: <38939DA2.6338F922@acm.org> References: <38939DA2.6338F922@acm.org> X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000130130139F.shin@nd.net.fujitsu.co.jp> Date: Sun, 30 Jan 2000 13:01:39 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem here is that ip6_fw.c is dependent upon INET6 instead of > IPv6FIREWALL. I sent mail to shin a little while ago about the > problem. If you want to compile a kernel in the interim, change the > line for ip6_fw.c in sys/conf/files to > > netinet6/ip6_fw.c optional ipv6firewall > > I believe this is the correct fix in any case. > > Jim Bloom > bloom@acm.org > > Kris Kennaway wrote: > > > > I get this whenever I try and build a kernel (with or without IPFIREWALL): Thanks for checking it! I fixed and committed it. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message