Local ParallelIO Build/Link with E3SM #6150
Closed
ackirby88
started this conversation in
E3SM model help
Replies: 2 comments 1 reply
-
We haven't tried E3SM builds with an installation of PIO outside the build directory (CESM might have this as a supported configuration). |
Beta Was this translation helpful? Give feedback.
1 reply
-
This does seem like a worthwhile thing to fix. We also build SCORPIO externally in a shared space for our Compass and Polaris packages, so it would be convenient if we could point Omega to these instead of redundantly building SCORPIO again each time we build Omega itself. It's not a major problem for us, just a matter of convenience. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi E3SM Team,
I've been able to build E3SM (maint-2.1) on the NCAR/NWSC Derecho system successfully and was able to run the test case
XS_2x5_ndays
. However, I had a few issues with linking a locally-installed version of ParallelIO.Inside
cime/CIME/build_scripts/buildlib.pio
, the comment states:I tried setting these four variables via my own
.bashrc
file, as well as in myrun_e3sm.derecho.sh
file via readonly variables. When setting thedo_case_build=true
, the compilation of e3sm.exe fails because it cannot finduse pio
for the Fortran files, as well as the all of the c-based functions used from the ParallelIO library. To get around this, I made symbolic links to thelibpioc.a
andlibpiof.a
static libraries in the{TEST_CASE}/build/<compiler>/mct/lib
directory.I was wondering the proper location for setting these
PIO
environment variables to get E3SM to pick up the local installation correctly? Thank you very much in advance!Beta Was this translation helpful? Give feedback.
All reactions