-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation on Mac Clang Issue? #20
Comments
Hi Sam, I think the issue you're getting is caused by a mistake I had present in the main branch for a couple hours yesterday. I believe it should be fixed now if you try to install again. Could you let me know if it works for you when you reinstall? Separately, I've been getting several reports that installing clang via conda is not working for people with older Macs. I've updated the instructions in that original issue here, to a recommendation that I tested successfully on a 2015 iMac. Basically, I installed everything via homebrew and didn't use conda for hdf5 or clang. From your current error messages, I don't think you should need to make changes to your compiler, hopefully it will work with the fix I added last night. |
I'm closing this for inactivity, but please do re-open or comment if you are continuing to have issues. I've been working on improving the installation process for Mac users, but I don't use a Mac as my daily computer so hearing feedback of what works and doesn't is especially helpful. |
Hi sounds good! Sorry I have been out of lab for bit so haven’t chance to try solution but will give it a go this week and report back. Best, |
Hi,
Trying to install the package and running into issue that at first seemed similar to #3. Following those instructions I ran clang install via conda and added lines to my RMakevars.
Now I no longer get the error about not having right compiler but I still get non-zero exit status and failed install. Full install warnings and errors and session info below.
Thanks!!
Sam
Build Messages
sessionInfo() output
The text was updated successfully, but these errors were encountered: