Install MOOSE in HPC cluster

[sidharthsarmah]

Hi @GiudGiud , I am trying to run jobs in HPC cluster using MOOSE, I followed these steps for condo https://mooseframework.inl.gov/getting_started/installation/conda.html but encountered some error to install MOOSE in it using https://mooseframework.inl.gov/getting_started/installation/hpc_install_moose.html, please suggest.

(moose) [sidharth@narval2 scripts]$ export MOOSE_JOBS=6 METHODS=opt
(moose) [sidharth@narval2 scripts]$ ./update_and_rebuild_petsc.sh
/home/sidharth/projects/def-jsong/sidharth/projects/moose/scripts
Submodule 'petsc' (https://gitlab.com/petsc/petsc.git) registered for path 'petsc'
Cloning into '/lustre06/project/6002274/sidharth/projects/moose/petsc'...
Submodule path 'petsc': checked out '1580af9fcba34756b20ac647dbc5659db3fdd05b'
INFO: Checking for HDF5...
INFO: HDF5 installation location was set using HDF5_DIR=/home/sidharth/miniforge/envs/moose
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The version of PETSc you are using is out-of-date, we recommend updating to the new release
 Available Version: 3.20.4   Installed Version: 3.20.3
https://petsc.org/release/download/
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
=============================================================================================
                         Configuring PETSc to compile on your system
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: CC=mpicc. Ignoring it! Use "./configure CC=$CC" if you really
  want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: CXX=mpicxx. Ignoring it! Use "./configure CXX=$CXX" if you
  really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: FC=mpif90. Ignoring it! Use "./configure FC=$FC" if you
  really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: F77=mpif77. Ignoring it! Use "./configure F77=$F77" if you
  really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: F90=mpif90. Ignoring it! Use "./configure F90=$F90" if you
  really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: CFLAGS=-march=nocona -mtune=haswell -ftree-vectorize -fPIC
  -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem
  /home/sidharth/miniforge/envs/moose/include. Ignoring it! Use "./configure
  CFLAGS=$CFLAGS" if you really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: CXXFLAGS=-fvisibility-inlines-hidden  -fmessage-length=0
  -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2
  -ffunction-sections -pipe -isystem /home/sidharth/miniforge/envs/moose/include
  -std=c++17. Ignoring it! Use "./configure CXXFLAGS=$CXXFLAGS" if you really want to use
  this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: FFLAGS=-march=nocona -mtune=haswell -ftree-vectorize -fPIC
  -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem
  /home/sidharth/miniforge/envs/moose/include. Ignoring it! Use "./configure
  FFLAGS=$FFLAGS" if you really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable:
  CPP=/home/sidharth/miniforge/envs/moose/bin/x86_64-conda-linux-gnu-cpp. Ignoring it! Use
  "./configure CPP=$CPP" if you really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: CPPFLAGS=-DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem
  /home/sidharth/miniforge/envs/moose/include. Ignoring it! Use "./configure
  CPPFLAGS=$CPPFLAGS" if you really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable: LDFLAGS=-Wl,-O2 -Wl,--sort-common -Wl,--as-needed
  -Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags -Wl,--gc-sections
  -Wl,--allow-shlib-undefined -Wl,-rpath,/home/sidharth/miniforge/envs/moose/lib
  -Wl,-rpath-link,/home/sidharth/miniforge/envs/moose/lib
  -L/home/sidharth/miniforge/envs/moose/lib. Ignoring it! Use "./configure
  LDFLAGS=$LDFLAGS" if you really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable:
  AR=/home/sidharth/miniforge/envs/moose/bin/x86_64-conda-linux-gnu-ar. Ignoring it! Use
  "./configure AR=$AR" if you really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Found environment variable:
  RANLIB=/home/sidharth/miniforge/envs/moose/bin/x86_64-conda-linux-gnu-ranlib. Ignoring
  it! Use "./configure RANLIB=$RANLIB" if you really want to use this value
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Using default C optimization flags "-g -O". You might consider manually setting optimal
  optimization flags for your system with COPTFLAGS="optimization flags" see
  config/examples/arch-*-opt.py for examples
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Using default Cxx optimization flags "-g -O". You might consider manually setting optimal
  optimization flags for your system with CXXOPTFLAGS="optimization flags" see
  config/examples/arch-*-opt.py for examples
=============================================================================================
=============================================================================================
                                     ***** WARNING *****
  Using default FC optimization flags "-g -O". You might consider manually setting optimal
  optimization flags for your system with FOPTFLAGS="optimization flags" see
  config/examples/arch-*-opt.py for examples
=============================================================================================
TESTING: configureMPI2 from config.packages.MPI(config/BuildSystem/config/packages/MPI.py:396)
*********************************************************************************************
           UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for details):
---------------------------------------------------------------------------------------------
  PETSc requires some of the MPI-2.0 (1997), MPI-2.1 (2008) functions - they are not
  available with the specified MPI library
*********************************************************************************************
There was an error. Exiting...
(moose) [sidharth@narval2 scripts]$ 

[GiudGiud]

your mpi seems too old?
what does the diagnostics script in moose/scripts return?

[milljm]

My only idea, is to use a later version of PETSc where this issue might have been fixed.

[sidharthsarmah]

Hi @milljm , can you suggest how do I do that?

[milljm]

Instead of cloning a specific version of MOOSE:

git clone --depth 1 --branch 2023-11-08 

You would just drop the--branch 2023-11-08 argument. You would then obtain the latest version of MOOSE (and with it, a more recent version of PETSc).

[GiudGiud]

what does this give

           UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for details):

please attach the configure.log

[sidharthsarmah]

Hi @GiudGiud @milljm , here it is:
configurelog.txt

[adityakavalur]

@sidharthsarmah and @milljm just to add my two cents in case its useful.

1. If you are trying to unload stickied modules module --force unload foo should do the trick, similarly module purge does not unload stickied modules you need to add the force flag for that as well, module --force purge, however that seems a bit excessive to me. The former will allow you to get to cleaner environments in a meaningful manner.
2. I would suggest trying without the StdEnv module and simply the base gcc, often times vendors/HPC admin will add a whole bunch of compiler flags and compiler wrappers on the base version through these modules.

[GiudGiud]

cd ../
cd solid_mechanics

then use the executable there.
In the future I would appreciate if you solved the simple problems yourself instead of going to the forum directly

[sidharthsarmah]

Sure @GiudGiud thanks but in case now I want to change my files in include or src folder to run using the solid_mechanics-opt, should I make -j6 in tensor mechanics or solid_mechanics folder. please suggest.

[GiudGiud]

in solid_mechanics.
tensor_mechanics is just here for compatibility with older applications

[sidharthsarmah]

Hi @GiudGiud , I transfer my .h and .C files in solid mechanics and proceeded to run my input file build using make -j6 but still getting error:

[GiudGiud]

change the registration in the ScheiderViscous.C file
make it to SolidMechanicsApp

[sidharthsarmah]

Hi @GiudGiud , I am getting this error when I try to make -j6 in my local laptop. Should I run update_and_rebuild_libmesh.sh in scripts folder.

Error:

(base) sidharthsarmah@Sidharths-MacBook-Air tensor_mechanics % make -j 6
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/libtool: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/libtool: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory

***WARNING***
Your libmesh is out of date.
You need to run update_and_rebuild_libmesh.sh in the scripts directory.

/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
Compiling C++ (in opt mode) /Users/sidharthsarmah/MOOSE/projects/moose/framework/build/unity_src/src_Unity.C...
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
Compiling C++ (in opt mode) /Users/sidharthsarmah/MOOSE/projects/moose/framework/build/unity_src/linesearches_Unity.C...
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/libtool: No such file or directory
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
make: *** [/Users/sidharthsarmah/MOOSE/projects/moose/framework/build/unity_src/src_Unity..opt.lo] Error 127
make: *** Waiting for unfinished jobs....
/bin/sh: /Users/sidharthsarmah/MOOSE/projects/moose/libmesh/installed/libtool: No such file or directory
make: *** [/Users/sidharthsarmah/MOOSE/projects/moose/framework/build/unity_src/linesearches_Unity..opt.lo] Error 127
(base) sidharthsarmah@Sidharths-MacBook-Air tensor_mechanics % 

[GiudGiud]

Currently do I need to remove the old version in HPC, how?:

just clone a new one

petsc/3.20.0
petsc/3.21.6
petsc/3.23.4

So unless you build petsc just for moose, you have to pick one of these three versions

[sidharthsarmah]

Hi @GiudGiud , could you suggest how to clone?:

[sidharth@login3 sidharth]$ module load scipy-stack/2023b
[sidharth@login3 sidharth]$ module load gcc/12.3
[sidharth@login3 sidharth]$ module load petsc/3.23.4 boost/1.82.0 eigen/3.4.0 
[sidharth@login3 sidharth]$ export GLPK_DIR=/cvmfs/soft.computecanada.ca/gentoo/2023/x86-64-v3/usr/lib64
[sidharth@login3 sidharth]$ git clone --depth 1 --branch 2023-11-08 https://github.com/idaholab/moose.git
fatal: destination path 'moose' already exists and is not an empty directory.
[sidharth@login3 sidharth]$ 

[GiudGiud]

git clone --depth 1 --branch 2023-11-08 https://github.com/idaholab/moose.git moose_new

into a new folder called moose_new

This is stuff chatGPT could help you with by the way

[sidharthsarmah]

Hi @GiudGiud thanks, I just did these but got the same modules:

[GiudGiud]

you went back to the moose folder, but the new clone is in the moose_new folder

[sidharthsarmah]

Hi @GiudGiud , I deleted the previous Moose folder and just created the new one to install it.

[bartoldeman]

@sidharthsarmah it's essential that you add
./update_and_rebuild_libmesh.sh --with-xdr-include=$EBROOTGENTOO/include/tirpc --with-glpk-include=$EBROOTGENTOO/include --with-eigen-include=$EBROOTEIGEN/include
as in the support email I sent you August 2025. Based on that, and another moose user we created a page with instructions as well:
https://docs.alliancecan.ca/wiki/Moose

[sidharthsarmah]

@sidharthsarmah it's essential that you add ./update_and_rebuild_libmesh.sh --with-xdr-include=$EBROOTGENTOO/include/tirpc --with-glpk-include=$EBROOTGENTOO/include --with-eigen-include=$EBROOTEIGEN/include as in the support email I sent you August 2025. Based on that, and another moose user we created a page with instructions as well: https://docs.alliancecan.ca/wiki/Moose

Hi @bartoldeman , I still got the errors:

-- Installing: /home/sidharth/projects/def-jsong/sidharth/moose/scripts/../framework/contrib/wasp/install/include/wasplsp/ThreadConnection.h
-- Installing: /home/sidharth/projects/def-jsong/sidharth/moose/scripts/../framework/contrib/wasp/install/include/wasplsp/WaspServer.h
-- Installing: /home/sidharth/projects/def-jsong/sidharth/moose/scripts/../framework/contrib/wasp/install/include/wasplsp/WaspServer.i.h
-- Installing: /home/sidharth/projects/def-jsong/sidharth/moose/scripts/../framework/contrib/wasp/install/scripts/test_moose_app_integration.sh
-- Up-to-date: /home/sidharth/projects/def-jsong/sidharth/moose/scripts/../framework/contrib/wasp/install/scripts/test_moose_app_integration.sh
[sidharth@login1 scripts]$ cd ../test
[sidharth@login1 test]$ make -j6
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/libtool: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/libtool: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
/bin/sh: line 1: /home/sidharth/projects/def-jsong/sidharth/moose/libmesh/installed/contrib/bin/libmesh-config: No such file or directory
Copying default MOOSE configuration to: /home/sidharth/projects/def-jsong/sidharth/moose/framework/include/base/MooseConfig.h...
Building and linking /home/sidharth/projects/def-jsong/sidharth/moose/python/pycapabilities/_pycapabilities.so...
bash: line 1: -DFOR_PYCAPABILITIES: command not found
make: *** [/home/sidharth/projects/def-jsong/sidharth/moose/framework/moose.mk:243: /home/sidharth/projects/def-jsong/sidharth/moose/python/pycapabilities/_pycapabilities.so] Error 127
make: *** Waiting for unfinished jobs....
[sidharth@login1 test]$ 

[bartoldeman]

Hi @sidharthsarmah I'll take this to our support system since it works for me, please watch your inbox

[GiudGiud]

we need the log from the libmesh installation too. this shows wasp then moose

[sidharthsarmah]

Thanks, it worked.

[bartoldeman]

@sidharthsarmah I think we are going around in circles here. Let me try myself on the same cluster and I'll get back to you.

[GiudGiud]

.sh not .h

[sidharthsarmah]

Hi @GiudGiud , I still got some errors:

[sidharth@login3 scripts]$ update_and_rebuild_wasp.sh
[sidharth@login3 scripts]$ cd ..
[sidharth@login3 moose]$ cd modules/solid_mechanics
[sidharth@login3 solid_mechanics]$ git clean -Xfd
Removing build/
[sidharth@login3 solid_mechanics]$ module load python scipy-stack petsc slepc vtk parmetis wasp eigen boost
export WASP_DIR=$EBROOTWASP
make -j 6

Lmod is automatically replacing "hdf5/1.14.6" with "hdf5-mpi/1.14.2".


Lmod is automatically replacing "netcdf/4.9.3" with "netcdf-mpi/4.9.2".


Lmod is automatically replacing "hdf5-mpi/1.14.4" with "hdf5/1.14.6".


Lmod is automatically replacing "netcdf-mpi/4.9.2" with "netcdf/4.9.3".

Lmod has detected the following error:  These module(s) or
extension(s) exist but cannot be loaded as requested: "hdf5-mpi/1.14.2"
   Try: "module spider hdf5-mpi/1.14.2" to see how to load the module(s).



Rebuilding symlinks in /home/sidharth/projects/def-jsong/sidharth/moose/modules/solid_mechanics/build/header_symlinks
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc...
Building and linking /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/hit.so...
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/exodiff/exo_entity.C...
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/exodiff/ED_SystemInterface.C...
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/exodiff/GetLongOpt.C...
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/exodiff/exoII_read.C...
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/exodiff/SL_tokenize.C...
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/exodiff/stringx.C...
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc: In member function 'void hit::Field::setVal(const std::string&, Kind)':
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:832:40: error: 'OVERRIDE_ASSIGN' is not a member of 'wasp'
  832 |                     ch.type() != wasp::OVERRIDE_ASSIGN))
      |                                        ^~~~~~~~~~~~~~~
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc: In function 'hit::Node* hit::parse(const std::string&, const std::string&, std::vector<ErrorMessage>*)':
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:1038:40: error: 'using element_type = class wasp::HITInterpreter<>' {aka 'class wasp::HITInterpreter<>'} has no member named 'error_diagnostics'
 1038 |     for (const auto & d : interpreter->error_diagnostics())
      |                                        ^~~~~~~~~~~~~~~~~
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc: In function 'void hit::buildHITTree(std::shared_ptr<wasp::HITInterpreter<> >, wasp::HITNodeView, Node*, std::string&, std::size_t&)':
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:1353:44: error: 'is_override' is not a member of 'wasp'
 1353 |         bool override_for_old_node = wasp::is_override(found_field->getNodeView());
      |                                            ^~~~~~~~~~~
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:1354:44: error: 'is_override' is not a member of 'wasp'
 1354 |         bool override_for_new_node = wasp::is_override(hnv_child);
      |                                            ^~~~~~~~~~~
Compiling C++ (in opt mode) /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/exodiff/exo_block.C...
make: *** [/home/sidharth/projects/def-jsong/sidharth/moose/framework/build.mk:152: /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.x86_64-pc-linux-gnu.opt.lo] Error 1
make: *** Waiting for unfinished jobs....
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc: In member function ‘void hit::Field::setVal(const std::string&, Kind)’:
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:832:40: error: ‘OVERRIDE_ASSIGN’ is not a member of ‘wasp’
  832 |                     ch.type() != wasp::OVERRIDE_ASSIGN))
      |                                        ^~~~~~~~~~~~~~~
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc: In function ‘hit::Node* hit::parse(const std::string&, const std::string&, std::vector<ErrorMessage>*)’:
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:1038:40: error: ‘using element_type = class wasp::HITInterpreter<>’ {aka ‘class wasp::HITInterpreter<>’} has no member named ‘error_diagnostics’
 1038 |     for (const auto & d : interpreter->error_diagnostics())
      |                                        ^~~~~~~~~~~~~~~~~
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc: In function ‘void hit::buildHITTree(std::shared_ptr<wasp::HITInterpreter<> >, wasp::HITNodeView, Node*, std::string&, std::size_t&)’:
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:1353:44: error: ‘is_override’ is not a member of ‘wasp’
 1353 |         bool override_for_old_node = wasp::is_override(found_field->getNodeView());
      |                                            ^~~~~~~~~~~
/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/src/hit/parse.cc:1354:44: error: ‘is_override’ is not a member of ‘wasp’
 1354 |         bool override_for_new_node = wasp::is_override(hnv_child);
      |                                            ^~~~~~~~~~~
make: *** [/home/sidharth/projects/def-jsong/sidharth/moose/framework/moose.mk:233: /home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/hit/hit.so] Error 1
[sidharth@login3 solid_mechanics]$ 

[GiudGiud]

you still did export WASP_DIR=$EBROOTWASP

you need to understand each command you type in. Use chatgpt to explain things if needed.

[sidharthsarmah]

Hi @GiudGiud , apology for the confusion, actually @bartoldeman mentioned using it to make:

yes before running "make" you'll need to reload the modules, otherwise you will run into errors (header files and libraries not found)

I redit it:

unset WASP_DIR
cd scripts
./update_and_rebuild_wasp.sh

and just did make -j 6 and it work:

[bartoldeman]

Hi,

the instructions on https://docs.alliancecan.ca/wiki/Moose specifically do NOT say to load a wasp module (which gives 4.2.0), so yes indeed you do NOT need to use $EBROOTWASP. The wasp built with ./update_and_rebuild_wasp.sh is 4.4.0.

However,

solid_mechanics-opt: error while loading shared libraries: libwaspplot.so.04: cannot open shared object file: No such file or directory

stems from solid_mechanics-opt not being able to find libwaspplot.so.04, which is part of wasp 4.4.0 but not 4.2.0. You'll have to modify LD_LIBRARY_PATH to be able to find it at run time:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/sidharth/projects/def-jsong/sidharth/moose/framework/contrib/wasp/install/lib