cstdlib error in Tutorial 1 #28216
cstdlib error in Tutorial 1
#28216
-
Check these boxes if you have followed the posting rules.
Issue or question about MOOSEI believe I am having the same issue as #25567 (but I do not think it was resolved) I am trying to do Tutorial 1, and upon creating new files for the new custom Kernels make no longer works (with the same error thrown). I am on this part of the tutorial: I am using an Apple Silicon M1 computer. (Optional) code in question / simulation log / errorsCompiling C++ (in opt mode) /Users/j/projects/babbler/build/unity_src/base_Unity.C...
Compiling C (in opt mode) /Users/j/projects/babbler/src/kernels/DarcyPressure.c...
In file included from /Users/j/projects/babbler/src/kernels/DarcyPressure.c:1:
In file included from /Users/j/projects/babbler/build/header_symlinks/DarcyPressure.h:4:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/ADKernelGrad.h:12:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/ADKernel.h:12:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/KernelBase.h:12:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/ResidualObject.h:12:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/MooseObject.h:13:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/MooseUtils.h:13:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/MooseTypes.h:12:
In file included from /Users/j/projects/moose/framework/build/header_symlinks/Moose.h:12:
In file included from /Users/j/miniforge/envs/moose/libmesh/include/libmesh/perf_log.h:25:
/Users/j/miniforge/envs/moose/libmesh/include/libmesh/libmesh_common.h:43:10: fatal error: 'cstdlib' file not found
#include <cstdlib>
^~~~~~~~~
1 error generated.
make: *** [/Users/j/projects/moose/framework/build.mk:180: /Users/j/projects/babbler/src/kernels/DarcyPressure.aarch64-apple-darwin20.0.0.opt.lo] Error 1
make: *** Waiting for unfinished jobs....Encountering Errors? Please include diagnostic output |
Beta Was this translation helpful? Give feedback.
Answered by
JonathanEdelmanS
Jul 25, 2024
Replies: 2 comments 8 replies
-
|
Hello Did you remember to conda activate the moose environment before building? Guillaume |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
How do I make sure to use mpich instead of openmpi? |
Beta Was this translation helpful? Give feedback.
-
|
conda info gives you additional details about the packages |
Beta Was this translation helpful? Give feedback.
-
|
Below is the list of packages from conda create -n moose moose-dev=2024.07.19 |
Beta Was this translation helpful? Give feedback.
-
|
let's try a previous version then |
Beta Was this translation helpful? Give feedback.
-
|
Ok I am using an older version of conda but the issue is still there. New diagnostics: |
Beta Was this translation helpful? Give feedback.
-
|
Resolved, accidentally had file ending in .c instead of .C |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
JonathanEdelmanS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Resolved, accidentally had file ending in .c instead of .C