Error with installation

[KhaledNabilSharafeldin]

Hello,
currently i'm updating the version of MOOSE I am currently using.
I'm following HPC install steps, and loading
cmake/3.20.6
gcc/10.2.0
openmpi/4.0.5
this compiles PETSc and libmesh just fine, but when i try running the tests, it doesn't detect the python installation. for that I need to load anaconda

however, whenever I try loading anaconda, installing PETSc fails with the error that there are no C compiler found.

any suggestions?

[GiudGiud]

Hello

If loading your conda environment comes with a set of compilers, a different MPI library, etc, then this will set it up for failure, as there will be conflicts between the modules you loaded and the conda packages.
Is there a python module you can load instead? Or a clean anaconda environment?

Guillaume

[KhaledNabilSharafeldin]

I figured out the issue with legacyParamsDefinition, if the original source doesnt have defineLegacyParam() it will not prompt an error to that specific file, instead, it'll prompt one of the files within the same folder regardless if it's following the new syntax or not.

still havent figured out what is the issue with using namespace exII

[KhaledNabilSharafeldin]

Defining the namespace as such solves the problem, thanks!

namespace exII {
extern "C" {
#include "libmesh/exodusII.h" // defines MAX_LINE_LENGTH, MAX_STR_LENGTH used later
}
}
using namespace exII;

marked as solved

[KhaledNabilSharafeldin]

Just a related question to the validity of the installation, whenever I compile the code i get this message at the very end.

/usr/bin/ld: warning: libhwloc.so.5, needed by /home/projects/moose/scripts/../libmesh/installed/lib/libmesh_opt.so, may conflict with libhwloc.so.15

is this something i should be worried about? Thanks again!

[GiudGiud]

Never had that particular one but had other libs with the same warning and it all went ok. Kudos for backwards compatibility for those developers

[GiudGiud]

I'm glad you figured those two out. It's unfortunate for the defineLegacyParam issue. This is almost completely disappeared now so we should never run into this again