Date: Tue, 10 Jun 2003 08:58:05 -0400 (EDT) From: Andre Guibert de Bruet <andy@siliconlandmark.com> To: Ian Freislich <ianf@za.uu.net> Cc: freebsd-current@freebsd.org Subject: Re: New Kernel Breaks IPFW Message-ID: <20030610085620.X56112@alpha.siliconlandmark.com> In-Reply-To: <5981.1055249140@mci.com> References: <20030610083242.S56112@alpha.siliconlandmark.com> <5981.1055249140@mci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Jun 2003, Ian Freislich wrote: > Andre Guibert de Bruet wrote: > > > > 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. With CFLAGS of -O -pipe and a conservative value of CPUTYPE (ie not p4), everything should be okay: It works here(tm)! ;-) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030610085620.X56112>