From owner-freebsd-ipfw@FreeBSD.ORG Wed Mar 24 15:08:37 2010 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66BFD1065670 for ; Wed, 24 Mar 2010 15:08:37 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 2CF718FC14 for ; Wed, 24 Mar 2010 15:08:36 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id C02F9730A1; Wed, 24 Mar 2010 16:18:31 +0100 (CET) Date: Wed, 24 Mar 2010 16:18:31 +0100 From: Luigi Rizzo To: Alexander Wittig Message-ID: <20100324151831.GB28594@onelab2.iet.unipi.it> References: <4BAA2627.8080203@wittig.name> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BAA2627.8080203@wittig.name> User-Agent: Mutt/1.4.2.3i Cc: freebsd-ipfw@freebsd.org Subject: Re: r205511 - ipfw.ko has unresolved symbols X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2010 15:08:37 -0000 On Wed, Mar 24, 2010 at 10:48:07AM -0400, Alexander Wittig wrote: > Hello > > Since the r205511 commit to 8-Stable my kernel can't load ipfw.ko any > more. The error message in dmsg is: > > kernel: link_elf_obj: symbol ipfw_dyn_attach undefined > kernel: linker_load_file: Unsupported file type > > A quick Google search for the first line brings up this message from > last December > (http://www.mail-archive.com/freebsd-ipfw@freebsd.org/msg02276.html): > > >On Thu, Dec 17, 2009 at 12:31:32PM -0500, David Horn wrote: > >> I am seeing a kldload failure for ipfw.ko after the latest -current > >commits > >> (fails for r200580 - r200633 inclusive) for ipfw: > >> > >> link_elf_obj: symbol ipfw_dyn_attach undefined > > > >not surprising, as i forgot to put the new filenames in the Makefile > >for the module, and buildworld does not (and cannot) complain about > >unresolved symbols. > > > >Just committed a fix in r200636 > > > >thanks > >luigi > > > > Is it possible that there is the same issue with this commit? definitely yes. thanks for the reminder. cheers luigi