Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Compile WRF V3.5.1 on Cheyenne

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.


New member
Recently I am trying to compile WRF V3.5.1 on Cheyenne to repeat some previous results, but failed.

The issue is that after the cpp converts the codes, the gnu copyright information was added into the code, so Fortran compilers can not handle it. An example is attached by end of this email.

Any suggestions are appreciated!

The below information was added into fortan codes after cpp convention.
/* Copyright (C) 1991-2014 Free Software Foundation, Inc.
This file is part of the GNU C Library.

The GNU C Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.

The GNU C Library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public
License along with the GNU C Library; if not, see
<>. */

Can you please attach your full compile log and your configure.wrf file so that I can take a look at those? Thanks!
Please see attached files. thanks.


  • compile.20.log
    817.1 KB · Views: 62
  • configure.wrf
    22.6 KB · Views: 53
There was a known problem with this version of the code, related to CPP. Take a look at this page:
At the top you will see modified tar files for V3.5.1. Download that file for WRF and try to compile again. You may also need to grab the WPS tar file if you plan to run real data cases.

You may want to try using either smpar or dmpar mode, instead of dm+sm. We don't do much testing with dm+sm and typically suggest not using it, as we have seen problems with it.

Let me know if you are able to build with the new version (and possibly with switching to dmpar or smpar). Thanks!