From owner-freebsd-stable@FreeBSD.ORG Thu Jan 31 05:28:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 685F016A418 for ; Thu, 31 Jan 2008 05:28:04 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 33B5C13C459 for ; Thu, 31 Jan 2008 05:28:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 9A8458EA33; Thu, 31 Jan 2008 00:28:03 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 31 Jan 2008 00:28:03 -0500 X-Sasl-enc: AQNMhu3FgQnL6nsnTqtPnBOiAyKcO//3ssURXBrdLvYJ 1201757283 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 057AF133FC; Thu, 31 Jan 2008 00:28:02 -0500 (EST) Message-ID: <47A15C62.3020201@incunabulum.net> Date: Thu, 31 Jan 2008 05:28:02 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.6 (X11/20070928) MIME-Version: 1.0 To: John Baldwin References: <479FE898.1030801@incunabulum.net> <200801301651.07643.doconnor@gsoft.com.au> <200801300904.35750.jhb@freebsd.org> In-Reply-To: <200801300904.35750.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: kldload: Unsupported file type X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2008 05:28:04 -0000 John Baldwin wrote: >>> It is printed whenever a kernel module is loaded. >>> The modules load OK. Nothing special or different about them. >>> >>> ... > The kernel is a link_elf type object I believe, so you have to have it. > > That follows (I was reading this the other day 'cause we don't support weak ELF symbols in the kernel for C++) however, why is the message being triggered now? Could it be ET_REL ? There have been no major changes to linking for the 6.3 buildkernel target IIRC. BTW only my amd64 system appears to be affected. later BMS