-
Notifications
You must be signed in to change notification settings - Fork 207
config_build migration guide
Sean Patrick Santos edited this page Aug 26, 2016
·
3 revisions
- Clean up any bugs in
config_compilers.xml
, e.g. bad XML, misspelled tags. When processing the CESM file, there were a few variables that should not have been in there (PIO_TYPENAME
, andADD_CPPDEFS
was misspelled asADD_CPPFLAGS
in some places). - Run
utils/perl5lib/compilers_translation_tool.pl
on theconfig_compilers.xml
file, and usexmllint
to make sure that the output matches theconfig_build
schema. The schema is located atcime_config/xml_schemas/config_build.xsd
. - Do as much BFB testing as reasonably possible, because we want to know if the compiler flags have changed from all of the above.
- Note that
<var>
tags may need to be replaced with<env>
tags, or vice versa, depending on whether a variable is intended to be used from the environment or from elsewhere inconfig_build
. - Note also that a generic setting that is overridden for a specific machine and
MPILIB
value needs to be overridden for allMPILIB
values. E.g. on yellowstone,SCC
is set to the same value asMPICC
forMPILIB="mpich2"
. Because this setting "hides" more generic settings, this means thatSCC
has to be set toifort
forMPILIB="mpi-serial"
.
- Note that
- Fix the comments in the output
config_build
file (they are likely to be in the wrong place, or possibly not correct at all).