lcpp-org / crane

A MOOSE application dedicated to general Chemical ReAction NEtworks for plasma chemistry and thermochemistry problems.
https://crane-plasma-chemistry.readthedocs.io/
GNU Lesser General Public License v2.1
21 stars 20 forks source link

symbol lookup error: #90

Closed ananthanarasimhanj closed 1 year ago

ananthanarasimhanj commented 1 year ago

I am getting the below error when I try to run the "argon_test.i" file.

../../crane-opt: symbol lookup error: /home/ananth/projects/moose/framework/libmoose-opt.so.0: undefined symbol: _ZN7libMesh14MacroFunctions12report_errorEPKciS2S2

cticenhour commented 1 year ago

Missing symbols generally means there is a "dirty" or incomplete library somewhere. In this case, it appears to be a missing symbol coming from libMesh. I would clean your CRANE installation first:

make clobberall

and then the answer changes based on how you are getting libMesh. If you are getting it from the MOOSE conda packages, make sure it's both up-to-date and active in your environment:

conda activate moose
conda update --all

Below is what you should see for a set of up-to-date conda packages when you perform a conda list (the second set of numbers is the version, and the most important here):

moose-libmesh             2023.01.09              build_0    https://conda.software.inl.gov/public
moose-libmesh-vtk         9.1.0               h6b51079_17    https://conda.software.inl.gov/public
moose-mpich               4.0.2                   build_7    https://conda.software.inl.gov/public
moose-petsc               3.16.6                  build_6    https://conda.software.inl.gov/public
moose-test-tools          2022.12.05      py310h39238f2_0    https://conda.software.inl.gov/public
moose-tools               2022.12.05      py310h39238f2_0    https://conda.software.inl.gov/public

If you are building libmesh yourself, I would go into your MOOSE installation and re-run the update_and_rebuild_libmesh.sh script.

After all this, then you should rebuild MOOSE and then CRANE.

smpeyres commented 1 year ago

@cticenhour I also spoke with @ananthanarasimhanj yesterday to fix this issue -> He updated and re-compiled MOOSE, did a fix relevant to the WSI he uses, and we got CRANE working again

ananthanarasimhanj commented 1 year ago

Thanks a lot @cticenhour @smpeyres.... It is resolved.