I've had pretty good success with packages.  I do, however, often times do
the following:

% sh
# nice -n 10 make 2>&1 | tee make.log

instead of just 'make'.  The 'nice -n 10' causes the build to run at a
lower priority so my old Mac IIci can still be somewhat responsive to
other windows.  The 2>&1 hooks up 'stderr' to the standard output.  The  
'| tee make.log'  causes all messages (normal and errors ones) to go both
to the screen and to a file called 'make.log'.  That way if something does
go wrong, I have a complete log of all the messages.  I've found this to
be effective when creating new packages.

-Dan


On Sat, 20 Mar 1999, Greg Evans wrote:

> Hi,
> 
> tried to install kde via the pkgsrc system a couple days ago, been busy 
> with other things, so it took a backseat to other things as far as 
> finding a solution.
> 
> Anyway, I positioned myself into the kde directory of the pkgsrc 
> directory (yes, getting myself into the computer was very difficult ;)) 
> typed 'make' and sat back.....A LONG time later, I finally had to sleep 
> and it was still compiling.  When I woke up in the morning I had a full 
> screen of *****STOP Error Code 1 and now way that I saw in afterstep to 
> scroll up and see what the problem was...  Is it common for pkgsrc stuff 
> to do this?  this is the second time I have had this happen, and don't 
> want to try again if there might be a problem with that particular 
> package.
> 
> Regards,
> 
> Greg
>