Move a couple more variable definitions to the top of a block

Added Makefile for contribs/sgi file.
Moved hypercube symbol definitions from select/linear to common.
Minor format changes for consistency with other Slurm code.
Moved a variable definition (l_distance) to start of code block
   to avoid error with some compilers.
Fix for possible uninitialized variable use (leftover_nodes).

Misplaced ";" resulted in bad tracking of BB user space usage

Ammendment to commit 744f114b

Fix race condition that could start a job that is dependent upon a job array
before all tasks of that job array complete.
bug 1324

Conflicts:
	src/sbatch/opt.c

Bug 1350

flag from a job while the job is waiting for a block to boot.

because of the referenced commit.  ntasks_set is always true on a BGQ at
this point.

Unify tracking of BB use on normal and abnormal terminations
Fix teardown race condition

Do not re-load state on a periodic basis as this will break our tracking until
  integrated with actual cray commands and we address race conditions
decrement usage counters when burst buffer teardown completes
Correct burst buffer string parsing for gres
Preeempt allocated buffers for higher priority jobs based upon GRES needs

Add streamlined test to see if a job has any burst buffer component
Add descripitive error if job node list not a valid cray "nid#" format
Replace _get_bb_size() with _get_bb_spec() to support GRES allocations
Fix GRES info pack for "scontrol get burst"
Add GRES allocations to common data structure
Track global GRES usage as allocations are made and removed
Log stage out failure
Gracefully handle bbs_pre_run error
Add some of the logic for preempting burst buffer allocations for higher priority jobs

This reverts commit abc435fd.

Bug 1346

a normal job.

in commit 501b8c1a.

This was broken by commit 2a5271c1
test16.4 was failing since sattach was not setting a protocol version.

Expanded --cpu-freq parameters to include min-max:governor specifications.
--cpu-freq now supported on salloc and sbatch.

Conflicts:
	NEWS

It largely prevents Slurm control over CPU frequency

This test failed once due to a low CPU frequency. Change the logic
to lessen the impact of a low frequency.