Re: Can't link kernel after recent libalias commits?
- From: Robert Watson <rwatson@xxxxxxxxxxx>
- Date: Sun, 31 Dec 2006 15:09:55 +0000 (GMT)
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
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- Can't link kernel after recent libalias commits?
- From: David Wolfskill
- Re: Can't link kernel after recent libalias commits?
- From: David Wolfskill
- Re: Can't link kernel after recent libalias commits?
- From: Paolo Pisati
- Re: Can't link kernel after recent libalias commits?
- From: Max Laier
- Re: Can't link kernel after recent libalias commits?
- From: Paolo Pisati
- Can't link kernel after recent libalias commits?
- Prev by Date: Re: Can't link kernel after recent libalias commits?
- Next by Date: FreeBSD 7.0 will use GCC 4.1 or 4.2?
- Previous by thread: Re: Can't link kernel after recent libalias commits?
- Next by thread: panic on pmap_remove_pages with INVARIANTS
- Index(es):
Relevant Pages
|
|