Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!darwin.sura.net!jvnc.net!netnews.upenn.edu!cronkite.ocis.temple.edu!astro.ocis.temple.edu!lafollet From: lafollet@astro.ocis.temple.edu (Paul Lafollette) Newsgroups: comp.unix.bsd Subject: Re: Compiling kernel from scratch takesa long time Message-ID: <1992Oct20.143450.5967@cronkite.ocis.temple.edu> Date: 20 Oct 92 14:34:50 GMT References: <1992Oct18.073316.3616@Saigon.COM> Sender: news@cronkite.ocis.temple.edu (NetWork News (readnews)) Organization: Temple University Lines: 42 X-Newsreader: Tin 1.1 PL5 David.Fox@Saigon.COM wrote: : 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've been meaning to post about this too. What I find is that when i rebuild from scratch (i.e. after deleting all objs) the compiler eventually hits what seems to be an infinite loop. If I control-C out of make, and then make again (restarting a compile of the same file) it once again compiles forever. Re-booting however and doing make, the offending file will re-compile in a few seconds. However, usually later on the same thing happens again with a different file. Again a re-boot fixes the problem. My guess as to what is happening is that there is a memory leak somewhere which causes the compiler to hang after doing a certain amount of work. Re-booting restores the memory (or swap space?) and allows more compiling to happen until the memory (or swap space?) fills up again. I have only seen this when re-compiling the kernel, but I haven't built anything else with that many files to compile all at once. I have installed all of the patches from the beta patch kit except for 47, the games patch, and the netstat things. If this is a known problem with a fix, I would be curious to know what it is. Thanks Paul Oh... to make my child happy: I have created the missing directory (/var/games) which made rogue unable to create a score file. However, now after two or three games of rogue, it writes garbage into the score file and the next time it tries to access it, it dumps core and crashes. Is this a known problem? Or is my kid the only 360BSD user who plays rogue? :)