Re: Buildkernel fails after cvsup and buildworld today (5.0 -> 5.1)any help?

2003-06-20 Thread Kent Stewart
On Friday 20 June 2003 04:53 pm, BSDVault wrote:
> I currently still booted into 5.0-RELEASE-p7.  My hardware is an asus
> A7M-266D dual AMD MP-1800's .  I have two Western Digital 120Gig drives
> (IDE) and 2 512 PC-2100 DDR.
>
> Buildworld completed fine after cd /usr/obj; chflags -R noschg * ; rm -rf
> *. I then tried to buildkernel as I always have and got the following
> error:
>
> machdep.o: In function `cpu_idle':
> machdep.o(.text+0x14a7): undefined reference to `sched_runnable'
> *** Error code 1
>
>

You didn't read /usr/src/UPDATING. The problem you are seeing is covered in 

20030125:
The scheduler framework has grown a second scheduler and consequently
you must specify one and only one scheduler in your kernel config.
The cvs config files have been updated to use the old scheduler
which may be selected via 'options SCHED_4BSD'.  If you would like
to try the new, much more experimental, scheduler please try
'options SCHED_ULE' and contribute to the arch@ discussion.

You probably should add  'options SCHED_4BSD' to your kernel config file.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Buildkernel fails after cvsup and buildworld today (5.0 -> 5.1)any help?

2003-06-20 Thread BSDVault
I currently still booted into 5.0-RELEASE-p7.  My hardware is an asus
A7M-266D dual AMD MP-1800's .  I have two Western Digital 120Gig drives
(IDE) and 2 512 PC-2100 DDR.

Buildworld completed fine after cd /usr/obj; chflags -R noschg * ; rm -rf *.
I then tried to buildkernel as I always have and got the following error:

machdep.o: In function `cpu_idle':
machdep.o(.text+0x14a7): undefined reference to `sched_runnable'
*** Error code 1 



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"