BUG FIX: p%mesh should be p_theta%mesh.  This was only a problem when using the viscous fs while testing the divergence using cv.  This is tested but apparently not in parallel when you can't get away with using the wrong global node numbering.
Obvious copy and paste bug.

I think this may fix the intel flredecomp bug for the cx1 tests, as I get the following 
backtrace (only for non-debugging build):
gdb) bt
#0  0x0000000000659f0b in state_module_mp_aliased_scalar_ ()
#1  0x000000000050950c in checkpoint_mp_checkpoint_fields_ ()
#2  0x00000000005072cb in checkpoint_mp_checkpoint_state_ ()
#3  0x0000000000507116 in checkpoint_mp_checkpoint_simulation_ ()
#4  0x0000000000503c5e in flredecomp ()
#5  0x000000000050419b in main ()
As per discussion at:
http://lists.gnu.org/archive/html/bug-libtool/2012-03/msg00004.html

libtool generation breaks for wrapped gfortran >=4.6 in some cases. This is
a different fix to the one proposed in the link above but seems to work. I'm
applying this directly to Fluidity to get a quick fix for Archer but will also
propose it as a fix to spud.
The current hack for building on ARCHER only works on the master node; 
rather than extending the hack to work on the slave nodes (which have far
more generic hostnames) this changes the behaviour to require a variable
to be set by the user, ARCHER.
Mea culpa; correcting an autoconf syntax error in my previous commit.
Expanding variables in the test XML command section as in some cases the 
variable assignment failed leading to a test failure.
Git-migration fixes

Deleting files that crept in during git-migration
Merge branch 'master' into fluidity-core/supportingsoftwaremanualupdates201403
First changes, altering bzr to git in the starter page.