Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!psgrain!ee.und.ac.za!shrike.und.ac.za!beastie.cs.und.ac.za!maltby
From: maltby@beastie.cs.und.ac.za (Gavin Maltby)
Newsgroups: comp.os.386bsd.questions
Subject: Odd behaviour recompiling kernel...help!
Date: 12 Oct 1993 07:12:07 GMT
Organization: University of Natal (Durban), South Africa
Lines: 45
Message-ID: <29dlc7$sfh@shrike.und.ac.za>
NNTP-Posting-Host: beastie.cs.und.ac.za
X-Newsreader: TIN [version 1.2 PL1]
Hi,
A month or so ago I posted a question concerning errors obtained when
recompiling the 0.9 kernel. The machine then had just been upgraded
by some others and I had no knowledge of the history of the machine
(e.g., who might have done what to it). Those problems were solved by
a disk crash---we did a complete re-install of 0.9 and all went well.
I compiled a custom kernel without problems not long after installation---
that kernel has been running for 1.5 weeks now. Yesterday I wanted
to change some parameters in the kernel, but I got the SAME errors
as I was getting before the disk crash! This time I know the history
of the machine, and I know who has fiddled where. Nobody has touched
the kernel source (in fact I even deleted and recopied the kernel
source just in case---same error).
Basically the error seems to be somewhere in the 'make depend', though it
only shows up in the subsequent 'make'. When it attempts the final link
('loading netbsd') I get an error 'subr_mcount.o: no such file'.
Now subr_mcount.c seems to be part of the core kernel (not an option).
Anyway, I compiled that separately and then it complains about another,
etc etc. When I compile all the little missing bits (about 8 in all)
and link them I get a dead kernel (not surprising, really!).
One can't even blame the config file for the new kernel---one gets the
same errors compiling the GENERICAHA kernel or recompiling the kernel
that is currently running.
Last time people said a was forgetting the 'make depend'. I really am not!
I typically do the ffg:
pwd is /sys/arch/i386/conf
config BEASTIE (the kernel name)
cd ../compile/BEASTIE
make depend | tee mkdep.log
make | tee mk.log
(and I tried without the tee's).
The 'make' gives the indicated error. Has anybody any guesses as to what
has happened here? I would be most grateful!
Thanks
Gavin