Cardinal with DAGMC build issues #1004
Replies: 2 comments
-
|
Hi Nancy, From what I can see, it looks like the linker errors you're encountering are caused by MOOSE and the MOOSE modules (which are independent of DAGMC). These are normally caused by mismatched header/source files (where a function definition in a C++ header doesn't match / is missing the corresponding function declaration in the source file); in your case I believe one of the following might be to blame:
My recommendation (given that you want to keep your working version of Cardinal) would be to delete the contents of If that doesn't end up working you can rebuild your working Cardinal installation with DAGMC. This can be done by running finally running Hope this helps, |
Beta Was this translation helpful? Give feedback.
-
|
I ended up using an older commit of the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
I am trying to again build Cardinal without MOOSE's conda environment but this time with
ENABLE_DAGMCset totrue. I have the 2 builds in 2 separate folders (/cardinaland/cardinal_dagmc) in my/home(just to keep things clean) and the one built without DAGMC works fine. However, the newer build is failing with the following error while linking thecardinal-optexecutable:How do I proceed?
My
/contrib/moose/scripts/diagnostics.shgives me a PASSED message so I understand that there's nothing wrong with the Python/conda environment setup.I am ignoring the
conda activate moose not performedwarning since I do not want to use the MOOSE'scondaenvironment as I want to be able to useNekRS.Are there any other diagnostics to perform that might point me in the right direction?
Beta Was this translation helpful? Give feedback.
All reactions