Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!agate!ames!sun-barr!cs.utexas.edu!usc!venice!gumby.dsd.trw.com!gumby.dsd.TRW.COM!gottloeb From: gottloeb@gumby.dsd.TRW.COM (Jeffery R. Gottloeb) Subject: Re: Compiling kernel from scratch takesa long time Message-ID: <1992Oct20.173908.29831@gumby.dsd.trw.com> Sender: news@gumby.dsd.trw.com Organization: TRW Space & Defense References: <1992Oct18.073316.3616@Saigon.COM> <1992Oct20.143450.5967@cronkite.ocis.temple.edu> Date: Tue, 20 Oct 1992 17:39:08 GMT Lines: 45 In article <1992Oct20.143450.5967@cronkite.ocis.temple.edu>, lafollet@astro.ocis.temple.edu (Paul Lafollette) writes: |> 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 |> I had this problem also. When the sum of the virtual sizes (VSZ) of all processes exceeds the amount of swap space (5Mb by default) the system just hangs without warning. I postponed the problem by manually creating a file system with a swap space of 16Mb. Jeff Gottloeb gottloeb@gumby.dsd.trw.com