custom kernel

[PJ]

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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at 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