-
|
I'm trying to install cardinal using the non-Conda install method as I'll be needing to use NekRS. I've come across a couple of Mac specific errors so far, but have come across a hurdle I can't seem to resolve. Any assistance from any Cardinal users would be greatly appreciated. Just a note in case it's useful in the future. I cam across an initial error that libtool wasn't being found. On Mac there is a different Libtool package preinstalled in /usr/bin/local. Running brew install libtool creates a package appended with a g at the start. I tried to symlink but this wasn't allowed on my machine. I just changed Following this I've re-run the I've exported them in my ~/.zshrc file: I've checked they are all installed using The versions of my compilers are:
When running the When looking at the config.log file I get: My system details are: Any help would be greatly appreciated |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Hi @Allentro, sorry to hear this is not going smoothly right out the gate. Because you are failing to build PETSc, that is actually not specific to Cardinal itself but rather it is an error you would also encounter if trying to build MOOSE. I am not sure on this one, but perhaps @milljm or @loganharbour have seen this? I do see this error towards the top, but perhaps it is a separate issue with HDF5. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @aprilnovak, thank you for the quick reply. Good point on the relevance, apologies there. I'm happy to close and move the discussion if you'd prefer? Regarding the HDF5 install, while doing most I had linked it to a local install on my machine, but clearly hadn't here. Exporting the HDF5_ROOT path I get the same error: |
Beta Was this translation helpful? Give feedback.
-
|
Because you are using Homebrew, you might have better luck not using Clang, but rather GCC instead. If that is an option? Clang 15 is pretty new... We usually stick with older, more stable (less bleeding edge) versions. For example, we are mostly using/testing with Clang 12 when operating on a Apple Silicon Mac. EDIT: Don't get me wrong, Homebrew is fantastic, so long if you are cautious with your brew updates and/or additional brew installs (which might underhandedly bump a version to something else in order to satisfy your install request), Homebrew is perfectly capable of being used for development. |
Beta Was this translation helpful? Give feedback.
-
|
I second @milljm's comment. Regarding HDF5, that looks good to me now - probably once the fortran compiler issue is resolved, you would have hit an error related to HDF5 so that aspect at least looks fixed. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the incredibly delayed response on this. You are right this appeared to be an issues with my clang versions for PetSc. I downgraded and this solved the problem, but it might have also been in combination with a few changes I made. Thank you for your help :) |
Beta Was this translation helpful? Give feedback.
-
|
Good timing! We're actually almost there (Supporting Clang 15): https://github.com/idaholab/moose/pull/26566/files#diff-7609acdf867b9dfc2a1678ea1b3acc2e1c54d7eae3a224e6171c7ddbbb29ed14 I am glad you got it sorted! |
Beta Was this translation helpful? Give feedback.
Because you are using Homebrew, you might have better luck not using Clang, but rather GCC instead. If that is an option? Clang 15 is pretty new... We usually stick with older, more stable (less bleeding edge) versions. For example, we are mostly using/testing with Clang 12 when operating on a Apple Silicon Mac.
EDIT:
Also Note: If you plan on sticking with Homebrew, just know that when you perform an update (in brew), and you happen to pull a new compiler, or dependency the Cardinal stack needs, you might need to re-build everything anew, as the old compiler/libraries will be lost with the brew update.
Don't get me wrong, Homebrew is fantastic, so long if you are cautious with your brew …