Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!ames!claris!szebra!David.Fox From: David.Fox@Saigon.COM Newsgroups: comp.unix.bsd Subject: Compiling kernel from scratch takesa long time Keywords: kernel compile Message-ID: <1992Oct18.073316.3616@Saigon.COM> Date: 18 Oct 92 07:33:16 GMT Organization: Station Zebra Corp, Sunnyvale CA Ph:408-739-1520 Lines: 32 Hi bsders, I got the kernel source code and started to compile the kernel from scratch. Everything was seemingly going smoothly until I noticed that the make was stuck trying to compile nfs/nfs_serv.c, and it was taking about 1 1/2 HOURS to compile this particular file. After this long time, I decided to try doing a suspend to see what was going on, but lost control over the machine and had to reboot. Basically my question is should it really take THIS LONG to compile one file? (It's about 34K in size.) Or is it a symptom of something pathological happening, like running out of memory? During this compile of the one file, the hard disk was doing considerable work. (I suppose compiling kernels can void the warranty on the hard drive?) :) I do have quite a few object files in YOURCONF, so the make was pretty happy until it got to that particular file. Is it just eating memory? One other question. I am using the GENERICISA configuration with one line added (for printer driver) and calling that YOURCONF, and I've configured, make depend'ed, and started make. During the make, I noticed that the flag -DNPX was added to each compilation line. Is this an indication that the kernel will want to see a math coprocessor? If it is, which line(s) should I change? (I don't have a math coprocessor.) Finally, my configuration: Packard Bell 386sx/16 4 megs RAM 130 meg IDE (ST-1144A), approximately 80 megs for 386bsd, rest is DOS 5 megs of Swap space kernel version 0.3 "borrowed"