Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1304 ; Tue, 23 Feb 93 14:34:33 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!gemini.oscs.montana.edu!osynw From: osynw@gemini.oscs.montana.edu (Nathan Williams) Subject: Re: [386BSD] unable to build kernel (0.2) Message-ID: <1993Feb13.202556.16436@coe.montana.edu> Keywords: n Sender: usenet@coe.montana.edu (USENET News System) Organization: Montana State University References: <110346@bu.edu> Date: Sat, 13 Feb 1993 20:25:56 GMT Lines: 35 In article <110346@bu.edu> heiser@acs.bu.edu (Bill Heiser) writes: > >I just installed the 0.2 patchkit, and removed patch602 >per the instructions. Now when I try to build my kernel, >it gets to the 'ld' and complains that "vers.o" doesn't >exist. This is reminiscent of a problem in the 0.1 >distribution! I thought this was fixed! Is there >something else I need to do? It seems like most 386BSD >things don't work as documented (I hate to say that). >But I guess that's to be expected in an "experimental OS" :-) Unfortunately, it's not well documented. However, any thing that has been patches needs to be re-compiled (kind of makes sense) In this instance, you need to re-compile config (/usr/src/usr.sbin/config) and then you won't see the vers.o problem after doing a make depend in your kernel compile directory. > >Also, the docs reference the "FILES" file to be used in determining >what "utilities and libraries" need to be rebuilt after installing >the patch. It isn't clear to me what "utilities and libraries" >need rebuilding... is there a list someplace? Everything in that list has been changed, and so therefore must be re-compiled. (Including config). However, to re-make the kernel only, you will only have to re-compile config. I would suggest re-making init also, though. Nate -- osynw@terra.oscs.montana.edu | A hacker w/out a home. work: (406) 994-5991 | Keeper of the Unofficial 386BSD Bug Report home: (406) 586-0579 | Please send bugs and/or fixes you find.