From owner-freebsd-current@FreeBSD.ORG Tue Jun 10 23:30:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85C1B37B401 for ; Tue, 10 Jun 2003 23:30:16 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA0E43FDD for ; Tue, 10 Jun 2003 23:30:16 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0s4.dialup.mindspring.com ([209.86.3.132] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19Pz7a-0003Yb-00; Tue, 10 Jun 2003 23:30:11 -0700 Message-ID: <3EE6CC27.DFF4C1D4@mindspring.com> Date: Tue, 10 Jun 2003 23:28:55 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Freislich References: <20030610083242.S56112@alpha.siliconlandmark.com> <5981.1055249140@mci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a478c07e41c9e965209d7ad0b5df2f8a51a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org cc: Andre Guibert de Bruet Subject: Re: New Kernel Breaks IPFW X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 06:30:16 -0000 Ian Freislich wrote: > Andre Guibert de Bruet wrote: > > Ian, > > > > The new ipfw binary will work with an up-to-date kernel. What you need to > > do is boot this new kernel and only then try out the new ipfw binary. > > That doesn't really explain why the new ipfw binary core dumped > with the new kernel, but worked fine with old kernels. > > Now that I've removed BDECFLAGS, it seems that my buildworld will > succeed and whatever it was that was broken that ipfw linked in > (statically) will hopefully be fixed and all will be good in my > land of -CURRENT, for the moment that is. It was the wrong header file; I said that before. When world is built, it uses the chroot installed header files that come from /usr/src/include; when you build an individual command in situ, it uses the old, stale, evil, nasty, bad, wrong header files from /usr/include. -- Terry