[ntp:hackers] scripts that might be handy

Hal Murray hmurray at megapathdsl.net
Thu Sep 17 05:02:50 UTC 2009

pogo:~murray/check-for-errors.sh greps for error patterns in A*/make.log
  flock-build currently makes 20 different copies of make.log
  Checking for errors by hand is likely to miss something due to operator 
  This is my attempt to avoid that.

pogo:~murray/local-build.sh runs flock_build on just the local system.
  Running flock-build on pogo takes a looooooong time, so I really want to 
catch all of the gross bugs before I get that far.  This lets you run the 4 
cases on your own system before wasting time on pogo.

The genetic diversity of the flock is pretty small these days.  This also 
lets you run it on your local environment(s).

Corrections/tweaks encouraged.  I'd be happy if somebody adopted them and 
merged them into the official recipe.

I don't really understand the build/flock-build area.

It requires that you don't run configure in the directory you are working in, 
but that's the normal part of my development cycle.

I assume there is another way, but I haven't figured it out yet.  Is there 
some simple idea I'm missing?

Currently, I setup another directory (bk clone/pull, bootstrap), copy the 
patches over and run test-build.sh there.  (I suppose that could be a good 
staging area for bits to send to pogo, but I haven't gotten that organized 

These are my opinions, not necessarily my employer's.  I hate spam.

More information about the hackers mailing list