Re: Kernel build problem after make world
HI, Sorry my information was somewhat obscure, you're answer however wasn't. The 4BSD_SCHED option did the trick. The real problem was mee being impatient trying to build a 5.2 KERNEL with a 5.0 config file. I made a new config file patiently copying lines in from NOTES and GENERIC. Now the world smiles again. :) Thnx for your help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel build problem after make world
On Tuesday 24 February 2004 03:43 am, [EMAIL PROTECTED] wrote: HI, Sorry my information was somewhat obscure, you're answer however wasn't. The 4BSD_SCHED option did the trick. I was kind of stretching on that one. It was the only sched option you were missing that I had and it stood out. The real problem was mee being impatient trying to build a 5.2 KERNEL with a 5.0 config file. I made a new config file patiently copying lines in from NOTES and GENERIC. Now the world smiles again. :) Thnx for your help. Great!! I think it is important to cp GENERIC to your kernel config for each major update. Then, start adding # in column 1 to comment out features. It may seem like work but it saves more time trying to figure out why something is broken. My systems are pretty simple when it comes to the configuration and I can take a GENERIC and convert it into a new config file in probably less than 5-10 minutes. If you keep a copy of the old one around, you can run diff on your old and new config and see what is different. When you start with a copy of GENERIC and delete features, your kernel config file is much more self documenting. Saving a few 100 bytes is not as important as keeping the structure of your config file so that people can key in very quickly on what you changed. This is especially true when you want free support :). I am retired but got talked into helping resurect an old project for a couple of weeks for an old friend. That dropped 8 hours a day from the time I had available to figure out FreeBSD errors. I simply didn't have the time to take a 5.2 GENERIC and see what you had chosen to use. 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]
Re: Kernel build problem after make world
On Sunday 22 February 2004 04:28 am, [EMAIL PROTECTED] wrote: Hi, I upgraded my system from RELEASE 5.0 to RELENG_5_2. Used cvsup to get the sources, made buildworld; made a generic kernel; installed world. Everything went well, i was able to boot into multi-user mode. BUT now i would like build a custom kernel. This doesnt work anymore. I tried it both ways. (make builkernel KERNCONF=MYKERNEL, or config MYKERNEL, make depend; make;) The kernel sources seem to compile, but when the linker starts my screen is flooded with unknown Unknown referernces errors Would anybody known what causes this? Should there be some magic new entry in /etc/make.conf? For starters, I think we would need to see the messages. What has me concerned is whether you installed your kernel before you did the installworld. Version 5.2 has a different statfs, which needs the new kernel to run. An old world and a new kernel was fine but an old kernel and a new world was a show stopper. You had to use the fixit disk to recover your system. There are different options in the config file for 5.2 and you would need to start with a new GENERIC to create your MYKERNEL. Beyond that, I don't have any ideas at this point. 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]
Re: Re: Kernel build problem after make world
Hi, you are right, should have included the messages in my first mail. Sorry. I followed the procedure in the handbook, make buildworld; make buildkernel; make installkernel; reboot; make installworld Intermediate that left me with a new kernel in an old world, which worked like i supposed it would. Is it possible one of the kernel options caused the messages? It doesn't seem to me, everything compiled ok, it's the linking process complaining. Missing header files?? All my kernel options (see below) seem also in either GENERIC or NOTES. again any help appreciated. Frans Jaspers [EMAIL PROTECTED] In my make.conf are only perl things. Here's my uname -a FreeBSD desktop.localnetwork 5.2.1-RC2 FreeBSD 5.2.1-RC2 #0: Sat Feb 21 22:18:28 GMT 2004 root@:/usr/obj/usr/src/sys/FJ_20040221_GENERIC i386 So that's the running new generic kernel. Here's the errors: $cd /usr/src $make buildkernel KERNCONF=FJ_20040221_01 -- Kernel build for FJ_20040221_01 started on Sun Feb 22 22:16:49 GMT 2004 -- === FJ_20040221_01 -- SNIP -- linking kernel init_main.o: In function `proc0_init': init_main.o(.text+0x2b9): undefined reference to `kse0_sched' init_main.o(.text+0x2c3): undefined reference to `ksegrp0_sched' init_main.o(.text+0x2cd): undefined reference to `proc0_sched' init_main.o(.text+0x2d7): undefined reference to `thread0_sched' kern_clock.o: In function `statclock': --- Many more - vm_pageout.o(.text+0x170c): undefined reference to `sched_nice' machdep.o: In function `cpu_idle': machdep.o(.text+0x151e): undefined reference to `sched_runnable' *** Error code 1 Stop in /usr/obj/usr/src/sys/FJ_20040221_01. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Here's my config file,
Re: Kernel build problem after make world
On Sunday 22 February 2004 03:00 pm, [EMAIL PROTECTED] wrote: Hi, you are right, should have included the messages in my first mail. Sorry. I followed the procedure in the handbook, make buildworld; make buildkernel; make installkernel; reboot; make installworld Intermediate that left me with a new kernel in an old world, which worked like i supposed it would. Is it possible one of the kernel options caused the messages? It doesn't seem to me, everything compiled ok, it's the linking process complaining. Missing header files?? I had to look at my 5.2-current system. I was hopping your kernel config was a commented version of GENERIC. That makes it much easier to see errors. With what you have listed, we can't see anything to trigger our memory of setup options. I wasn't surprised to not see someone respond to your message. You made it really difficult :). For starters, I think you need the following line options SCHED_4BSD #4BSD scheduler There may be other errors but I didn't have time enough to look at the rest of your configuration. Kent All my kernel options (see below) seem also in either GENERIC or NOTES. again any help appreciated. Frans Jaspers [EMAIL PROTECTED] In my make.conf are only perl things. Here's my uname -a FreeBSD desktop.localnetwork 5.2.1-RC2 FreeBSD 5.2.1-RC2 #0: Sat Feb 21 22:18:28 GMT 2004 root@:/usr/obj/usr/src/sys/FJ_20040221_GENERIC i386 So that's the running new generic kernel. Here's the errors: $cd /usr/src $make buildkernel KERNCONF=FJ_20040221_01 -- Kernel build for FJ_20040221_01 started on Sun Feb 22 22:16:49 GMT 2004 -- === FJ_20040221_01 -- SNIP -- linking kernel init_main.o: In function `proc0_init': init_main.o(.text+0x2b9): undefined reference to `kse0_sched' init_main.o(.text+0x2c3): undefined reference to `ksegrp0_sched' init_main.o(.text+0x2cd): undefined reference to `proc0_sched' init_main.o(.text+0x2d7): undefined reference to `thread0_sched' kern_clock.o: In function `statclock': --- Many more - vm_pageout.o(.text+0x170c): undefined reference to `sched_nice' machdep.o: In function `cpu_idle': machdep.o(.text+0x151e): undefined reference to `sched_runnable' *** Error code 1 Stop in /usr/obj/usr/src/sys/FJ_20040221_01. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Here's my config file, machine i386 cpu I686_CPU ident FJ_20040221_01 maxusers0 options INET options INET6 options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options MD_ROOT options NFSCLIENT options NFSSERVER options NFS_ROOT options MSDOSFS options CD9660 options PROCFS options PSEUDOFS options COMPAT_43 options COMPAT_FREEBSD4 options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV options INVARIANT_SUPPORT device isa device eisa device pci device pci device fdc device ata device atadisk device atapicd device atapifd options ATA_STATIC_ID device atkbdc device atkbd device psm device vga device splash device sc device agp device npx device pmtimer device sio device ppc device ppbus device lpt device ppi device miibus device vr device random device loop device ether device ppp device tun device pty device md device gif device faith device uhci device usb device ugen -- 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]
