MOOSE Bulid Problem #25789
Answered
by
GiudGiud
ljeft
asked this question in
Q&A Getting Started
MOOSE Bulid Problem
#25789
-
|
Hello I tried running the command Any advice would be really appreciated. |
Beta Was this translation helpful? Give feedback.
Answered by
GiudGiud
Oct 29, 2023
Replies: 2 comments 15 replies
-
|
Hello Let s get a printout from the diagnostics script in moose/scripts please and I ll take a look tomorrow |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
did you unload our mamba packages? i dont see our mpi in the diagnostics anymore you can use either mpi, but only one needs to be available when you install |
Beta Was this translation helpful? Give feedback.
-
|
Not just GCC, this seems to be a different machine than the last log... CPU count is different, arch is different, etc. Also, do be careful running as the |
Beta Was this translation helpful? Give feedback.
-
|
I installed moose according to the method of [this URL](url), I did not install conda, so I do not know how to solve this problem |
Beta Was this translation helpful? Give feedback.
-
|
ok this makes more sense. This is one this is the initial one used is most likely in this I would
All in one session. |
Beta Was this translation helpful? Give feedback.
Answer selected by
ljeft
-
|
Excuse me, @GiudGiud and @milljm ,when I "make -j 8 " in /moose/test, it's a fatal error that Jiahuilv |
Beta Was this translation helpful? Give feedback.
6 replies
-
|
Thanks,I have tried it, but it's no use. I don't know why it is also missing the filesystem.
JiahuiLv. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, to solve this problem, I upgraded gcc from 7.5 to version 10.4, but it seems to have a new issue. When I installed libmesh after completing the installation of petsc, it seemed to think that I had not installed petsc.How to solve this . |
Beta Was this translation helpful? Give feedback.
-
|
You will have to find a way to get the full output of this libmesh build, and post it as an attachment. There is too much information involved throughout the file to be resolved with pictures of portions of the log. Please attache the following files: |
Beta Was this translation helpful? Give feedback.
-
|
Also, please... do not post new questions to already answered questions (like you did here). I will allow you to post to this thread, but please let this be the last time. The reason for this is simple: When people search for:
Specifically this error: Each discussion, can only have one answer. |
Beta Was this translation helpful? Give feedback.
-
|
Let's continue on another post. You have an error about "no Python" in the libmesh log before any petsc issues. This will need to be addressed Then the last errors are probably due to the change in compiler. After a change in compiler you need to thoroughly clean the repo to get rid of old compiled files. Use "git clean -xfD" and use it for every submodule and nested submodules as well |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ok this makes more sense.
The problem is that you have two MPI distributions available still. And one was used for compilation earlier, then the other one was
This is one
this is the initial one used is most likely in this
compiler/dtk/22.10.1module.I would
update_and_rebuild_petsc.shagain in moose/scriptsAll in one session.