From owner-freebsd-questions@FreeBSD.ORG Sat Dec 6 02:22:03 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37094106564A for ; Sat, 6 Dec 2008 02:22:03 +0000 (UTC) (envelope-from af.gourmet@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 0D9EE8FC0A for ; Sat, 6 Dec 2008 02:22:02 +0000 (UTC) (envelope-from af.gourmet@videotron.ca) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from [192.168.0.52] ([96.21.103.185]) by VL-MH-MR001.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0KBF0060ZNWQSX20@VL-MH-MR001.ip.videotron.ca> for freebsd-questions@freebsd.org; Fri, 05 Dec 2008 21:22:02 -0500 (EST) Message-id: <4939E1C9.8000701@videotron.ca> Date: Fri, 05 Dec 2008 21:22:01 -0500 From: PJ User-Agent: Thunderbird 2.0.0.17 (X11/20081128) To: nightrecon@verizon.net References: <4939D0FB.9090304@videotron.ca> In-reply-to: Cc: freebsd-questions@freebsd.org Subject: Re: custom kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2008 02:22:03 -0000 Michael Powell wrote: > PJ wrote: > > [snip] > > Read carefully: > >> uvscom.o (.text+0x293): In function 'uvscom_attach' ; >> :undefined reference to 'ucom_attach' etc..... >> *** Error code 1 > > See further down at bottom. > >> did I do something wrong? system is still on and functioning but how do >> I make the custom kernel? > > The canonical first thing to do is to see if your system will build GENERIC. > If it does not you have done something to the OS. If GENERIC builds OK > and your custom kernel config will not, there is something broken with your > config file. Remember to cd /usr/obj and rm -rf usr or make clean first. > Always clean out the stale leftovers prior to build. > >> this is my kernel file: >> >> # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.7 2008/04/10 22:09:22 >> rwatson Exp $ > > I'm at home and only have two GENERIC conf files to look at. > RELENG_7: > > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.15 2008/11/24 00:52:26 yongari Exp $ > > RELENG_7_0: > > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.2.2.1 2008/02/06 03:24:28 scottl Exp $ > > >> cpu I686_CPU >> ident MYKERNEL >> >> # To statically compile in device wiring instead of /boot/device.hints >> #hints "GENERIC.hints" # Default places to look for devices. > [snip] >> # USB Serial devices >> #device ucom # Generic com ttys > [snip] >> device uvscom # USB serial support for DDI pocket's PHS > [snip] > > Read the error message. It is failing to build uvscom because uvscom > depends on #device ucom and you have ucom commented out. > > > -Mike > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > Can't u;nderstand where this stuff came from... I normally had that stuff commented out. I even found the same error on the older, functional machine's kernel which had compiled correctly.... there was another error in that kernel at the very beginning - the SCHEDULE_4BSD was SCHEDULE_UNO or something like that.. but it was commented out...perhaps these glitches happened through some kind of accidental typos in vi.... Anywasy, I think that will fix things... thank you for the observations. Phil Jourdan