From owner-freebsd-current@FreeBSD.ORG Sun Dec 31 15:28:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35C2116A407; Sun, 31 Dec 2006 15:28:43 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id CE5A513C428; Sun, 31 Dec 2006 15:28:40 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5205E4881E; Sun, 31 Dec 2006 10:09:55 -0500 (EST) Date: Sun, 31 Dec 2006 15:09:55 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Paolo Pisati In-Reply-To: <20061231024203.GA8147@tin.it> Message-ID: <20061231150906.U7974@fledge.watson.org> References: <20061230195219.GD64111@bunrab.catwhisker.org> <20061230214321.GG64111@bunrab.catwhisker.org> <20061230214609.GA6996@tin.it> <200612302304.39194.max@love2party.net> <20061231024203.GA8147@tin.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Max Laier , freebsd-current@freebsd.org Subject: Re: Can't link kernel after recent libalias commits? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 31 Dec 2006 15:28:43 -0000 On Sun, 31 Dec 2006, Paolo Pisati wrote: > 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. Yes -- I'd prefer it if we could make LIBALIAS optional for IPFW, similar to dummynet, ipdivert, etc. Is this something done without too much trouble? Robert N M Watson Computer Laboratory University of Cambridge