Amit Uttamchandani wrote: > Hi, > > I have a fairly old laptop (500MHz G4) and I tend to compile a lot of > applications from source. Most of time it doesn't take too long but > when I compile large libraries or applications this sometimes takes 4-5 > hours. > > An example is webkitgtk+ 1.1.3. I needed this to compile the latest > version of midori. After a couple of hours of compilation, I paused the > job using Ctrl-Z and suspended my laptop to RAM. The next morning, I > resumed the laptop and typed 'fg' to resume the compile. To my > surprise, it worked fine and I was able to compile and install > webkitgtk+ successfully. > > Now, I am thinking of applying this to kernel compilation, etc. Is this > common practice? Do others do this as well?
Just thought I would give my 2 cents on this. For long compilations, I do it in the background along with nohup. It works great. The command line looks like nohup make 2>&1 | tee make.log & That way the program runs in the background, output is redirected to a file, compilation goes on even after log out. hth raju -- Kamaraju S Kusumanchi http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
