From owner-freebsd-current@FreeBSD.ORG Mon May 21 08:51:45 2007 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 EB71416A46B; Mon, 21 May 2007 08:51:45 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.freebsd.org (Postfix) with ESMTP id C955413C48C; Mon, 21 May 2007 08:51:45 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4L8pj9i025478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 May 2007 01:51:45 -0700 X-Auth-Received: from [192.168.10.45] (c-67-166-149-71.hsd1.ca.comcast.net [67.166.149.71]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4L8piOa020422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 May 2007 01:51:44 -0700 Message-ID: <46515D9F.1080908@u.washington.edu> Date: Mon, 21 May 2007 01:51:43 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: "Wojciech A. Koszek" , freebsd-current@freebsd.org References: <20070521074413.GL61558@ns2.wananchi.com> <20070521083438.GA91554@FreeBSD.czest.pl> In-Reply-To: <20070521083438.GA91554@FreeBSD.czest.pl> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.5.21.13237 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: Subject: Re: Kernel compilation failure ... 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: Mon, 21 May 2007 08:51:46 -0000 Wojciech A. Koszek wrote: > On Mon, May 21, 2007 at 09:51:52AM +0200, Claus Guttesen wrote: >>> I am running -CURRENT on my desktop, csup-ped sources even today >>> - 20070521. >>> For the last one week or so, I cannot successfully compile a kernel. >>> Always fails here: >>> >>> >>> cc -shared -nostdlib hack.c -o hack.So >>> rm -f hack.c >>> MAKE=make sh /usr/src/sys/conf/newvers.sh alligator >>> cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs >>> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >>> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. >>> -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL >>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common >>> -finline-limit=8000 --param inline-unit-growth=100 --param >>> large-function-growth=1000 -mno-align-long-strings >>> -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 >>> -mno-sse3 -ffreestanding vers.c >>> linking kernel.debug >>> if_ural.o(.text+0xe8f): In function `ural_attach': >>> /usr/src/sys/dev/usb/if_ural.c:491: undefined reference to >>> `ieee80211_amrr_init' >>> if_ural.o(.text+0x2fa5): In function `ural_task': >>> /usr/src/sys/dev/usb/if_ural.c:2360: undefined reference to >>> `ieee80211_amrr_node_init' >>> if_ural.o(.text+0x3179): In function `ural_amrr_update': >>> /usr/src/sys/dev/usb/if_ural.c:2418: undefined reference to >>> `ieee80211_amrr_choose' >>> *** Error code 1 >> Something with a wireless usb-card in your kernel-config maybe? Is it >> ALLIGATOR a copy of GENERIC or customized? > > Presence of ural(4) and lack of the wireless support seems to be the > cause of the problem. Try to check if you have wlan(4) present. > This is the most comment cause for error in compiling custom kernels I've seen (the OP is around the 20th person I've seen while semi-actively watching the lists for the past year or so). I think that the questions and current lists should have FAQs about this particular "error", or maybe the example GENERIC kernel config file should move ural to the wlan section and have a big warning posted next to it stating "ural requires both USB and wlan support". Just my thought though on the subject.. -Garrett