Ok, thanks for the quick feedback! Actually compiling from standalone CAM scripts made me problems worse -- I run into a host of fortran compiler issues because the makefile generated by CAM's (standalone) configure program doesn't know the details of the machine on which I am running. I spent 2 days with a colleague trying to figure out which fortran flags need to be added to the make file to make CAM compile, but to no avail -- no matter what we do, there is always some mysterious complaint about the code.
For a standard CESM build, we just skirt this issue because we define the machine when we build the case, and then ./configure -case reads the macros file that is defined for our machine. What I don't understand is how to configure CAM alone (using the cam scripts) and still get it to read this Macros file, or at least get it to accept the settings for our system. [FYI, I'm running on the AIX machine Blizzard at the DKRZ in Hamburg, Germany.]
So in summary I'm running into two separate problems, and now sure which is better to tackle
(1) building CAM standalone using the standard CESM run scripts fails if I try to set MPI_SERIAL = TRUE.
(2) building CAM using its own build scripts fails because I don't know how to get the fortran settings of the machine I'm using to be "read" during the configuration.