About the Step 5 in tutorial, I get Fatal error: <string> no such file or directory #26415
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Hello could you please run the diagnostics script in mosoe/scripts? Guillaume |
Beta Was this translation helpful? Give feedback.
-
Because of your kernel file extension the compiler is attempting to compile moose in c, rather than its natural c++ language. The kernel file should be '.C' (uppercase dot c) and not '.c' (lowercase dot c). This issue here has a similar cause and effect: #18050 This is what a successful output looks like. Note that it says 'Compiling C++' rather than C, as it does with your attempts. (moose) neutralchaos@neutralchaos-To-be-filled-by-O-E-M:~/projects/babbler$ make -j 4
Checking if header needs updating: /home/neutralchaos/projects/moose/framework/include/base/MooseRevision.h...
Creating Unity /home/neutralchaos/projects/babbler/build/unity_src/kernels_Unity.C
Compiling C++ (in opt mode) /home/neutralchaos/projects/babbler/build/unity_src/kernels_Unity.C...
Linking Library /home/neutralchaos/projects/babbler/lib/libbabbler-opt.la...
Linking Executable /home/neutralchaos/projects/babbler/babbler-opt...
(moose) neutralchaos@neutralchaos-To-be-filled-by-O-E-M:~/projects/babbler$ For what its worth, I was stuck on this issue for a few days as well. |
Beta Was this translation helpful? Give feedback.
Because of your kernel file extension the compiler is attempting to compile moose in c, rather than its natural c++ language. The kernel file should be '.C' (uppercase dot c) and not '.c' (lowercase dot c).
This issue here has a similar cause and effect: #18050
This is what a successful output looks like. Note that it says 'Compiling C++' rather than C, as it does with your attempts.