Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Jun 2003 23:28:55 -0700
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Ian Freislich <ianf@za.uu.net>
Cc:        Andre Guibert de Bruet <andy@siliconlandmark.com>
Subject:   Re: New Kernel Breaks IPFW
Message-ID:  <3EE6CC27.DFF4C1D4@mindspring.com>
References:  <20030610083242.S56112@alpha.siliconlandmark.com> <5981.1055249140@mci.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EE6CC27.DFF4C1D4>