Date: Sun, 31 Dec 2006 03:42:03 +0100 From: Paolo Pisati <piso@freebsd.org> To: Max Laier <max@love2party.net> Cc: freebsd-current@freebsd.org Subject: Re: Can't link kernel after recent libalias commits? Message-ID: <20061231024203.GA8147@tin.it> In-Reply-To: <200612302304.39194.max@love2party.net> References: <20061230195219.GD64111@bunrab.catwhisker.org> <20061230214321.GG64111@bunrab.catwhisker.org> <20061230214609.GA6996@tin.it> <200612302304.39194.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 30, 2006 at 11:04:33PM +0100, Max Laier wrote: > On Saturday 30 December 2006 22:46, Paolo Pisati wrote: > > On Sat, Dec 30, 2006 at 01:43:21PM -0800, David Wolfskill wrote: > > > Note that this was for a kernel that uses ipfw, but not natd (ref. > > > src/sys/conf/NOTES). > > > > my mistake, i'll write an entry for UPDATING. > > Shouldn't it still be possible to build a kernel with IPFW but without > LIBALIAS? i.e. instead of a UPDATING entry you should just wrap the > libalias entry points in IPFW - or am I misunderstanding what you are > saying? with my last commit, LIBALIAS became mandatory for IPFW, and this adds 40kb (-O nocona) to my kernel size. If it's really an issue, i can change it. P.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061231024203.GA8147>