Running make -j8 is not producing cardinal-opt file, ModuleNotFoundError: No module named 'TestHarness', and ModuleNotFoundError: No module named 'hit'

[lliw-will]

I followed the Building Cardinal without MOOSE's conda Environment directions as I require NekRS; however, after running make there is no cardinal-opt despite the process seemingly running in its entirety. There was an error saying GLIBCXX_3.4.32 was not found and there was no module named 'hit'. When I attempted to run the run_tests file I got an error saying no module named 'TestHarness'.

Any help with these problems would be greatly appreciated.

[aprilnovak]

Hi @lliw-will, if no cardinal-opt was produced it means that the build command was not successful. Oftentimes, the actual error message gets buried in the screen output and won't be immediately obvious. Would you please do the following:

cd cardinal
rm -rf build/ install/
make -j8  >> out.txt 2>&1

and then attach out.txt here?

[aprilnovak]

Hi @lliw-will, sorry for the delayed response, I was out of office all of last week.

If you're willing to attempt a fresh Linux install, that could be an option to get to the bottom of this. I've always used macOS so I don't have any first-hand advice on which distribution to choose, but I know some folks have used Linux Mint successfully.

[lliw-will]

I apologize for the time it took me to respond earlier as I was away for a couple of workshops.

After installing Mint-cinnamon and going through the build guide for a CPU build the results were as follows: out_mint_CPU.txt

[aprilnovak]

I recently encountered linking issues from the solid mechanics module, and was able to fix it by deleting Cardinal and starting over with a fresh clone (not a satisfying explanation, but I think that will work for you). Also please make sure you are using the MOOSE hash tied to Cardinal (i.e., you're not setting anything custom for MOOSE_DIR).

[lliw-will]

Good news @aprilnovak, I deleted Cardinal and tried building again and the cardinal-opt file was created. This time I had used the main terminal instead of the one used by visual studio code.

Is it possible to build with the CUDA backend without removing the current build?

[aprilnovak]

No, MOOSE's build setup does not allow out-of-source builds (so any time a build configuration is changed, the entire build directory must be re-created). Fortunately, the most time-consuming process is building PETSc and libMesh, which do NOT need to be repeated if you'd like to add CUDA.

cd cardinal
rm -rf build/ install/
# edit Makefile to set OCCA_CUDA_ENABLED=1
make -j8