Skip to content

Conversation

@jjokella
Copy link
Contributor

@jjokella jjokella commented Jul 11, 2025

Started from issue #81

Opening PR for testing CI.

Related: HPSCTerrSys/pdaf#30

@jjokella jjokella added PDAF Involves PDAF CI labels Jul 11, 2025
jjokella added 8 commits July 11, 2025 11:16
includes: commenting out unused variables in PDAF code
in order to get Oasis-files compiled correctly
Error
```
parflow_pdaf/pfsimulator/parflow_lib/solver_richards.c:1817:16: error:
unused variable ‘pfl_start’ [-Werror=unused-variable]
```

Background: In `PseudoAdvanceRichards`, there are many unused
variables.
branch matching current generic ParFlow from TSMP2
@kvrigor
Copy link
Member

kvrigor commented Jul 16, 2025

The issue seems to be the way ParFlow linker flags are manually specified:

if(DEFINED PARFLOW_SRC)
list(APPEND PDAF_LIBS "-L${CMAKE_INSTALL_PREFIX}/lib -lpfsimulator -lamps -lpfkinsol -lgfortran -lcjson")
# GPU
# list(APPEND PDAF_LIBS "-L${CMAKE_INSTALL_PREFIX}/rmm/lib -lstdc++ -lcudart -lrmm -lnvToolsExt")
list(APPEND PDAF_LIBS "-L${HYPRE_ROOT}/lib -lHYPRE")
list(APPEND PDAF_LIBS "-L/lib64 -lslurm")
endif()

The correct linker flags for ParFlow 3rd party dependencies (e.g. CUDA, Hypre) are generated by the ParFlow CMake scripts. Unfortunately TSMP2 cannot directly access these flags since they are dynamically generated. We need to find a way to extract these linker info from ParFlow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI PDAF Involves PDAF

Projects

None yet

Development

Successfully merging this pull request may close these issues.

eCLM-ParFlow-PDAF: HYPRE/SLURM library linking issue

3 participants