What happened?
Several users have reported build failures relating to TUV-x -- it seems this is tied to the FindPackage call for yaml-cpp, so this introduces a one-line change to force CAM to build this itself, avoiding incompatible versions/environments.
What are the steps to reproduce the bug?
On Derecho, 'module load conda; conda activate; ./case.build' after configuring a case.
(It's more problematic for people who have conda activated by default, since it propagates to qcmd-based builds.)
What CAM tag were you using?
cam_development
What machine were you running CAM on?
CISL machine (e.g. cheyenne)
What compiler were you using?
Intel
Path to a case directory, if applicable
No response
Will you be addressing this bug yourself?
Yes
Extra info
No response
What happened?
Several users have reported build failures relating to TUV-x -- it seems this is tied to the FindPackage call for yaml-cpp, so this introduces a one-line change to force CAM to build this itself, avoiding incompatible versions/environments.
What are the steps to reproduce the bug?
On Derecho, 'module load conda; conda activate; ./case.build' after configuring a case.
(It's more problematic for people who have conda activated by default, since it propagates to qcmd-based builds.)
What CAM tag were you using?
cam_development
What machine were you running CAM on?
CISL machine (e.g. cheyenne)
What compiler were you using?
Intel
Path to a case directory, if applicable
No response
Will you be addressing this bug yourself?
Yes
Extra info
No response