-
Notifications
You must be signed in to change notification settings - Fork 16
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
Running GLM under macOS Sierra #119
Comments
Update: I have gotten GLM from the website working by manually installing intel fortran redistributable and NCDF libraries manually and pointing at them using |
I've been able to reproduce the GLMr failure on about ~20 OS X machines, all Sierras or El Cap. The previous work-around by disabling SIP is no longer working- do you have any suggestions for how to get around this issue? I'm still able to run GLMr v.2.1.8 on my El Cap machine using R v.3.3 but not 3.4, if that's useful. |
Update: I can run GLMr v.3.1.14 on El Cap and Sierra OS X machines using R v.3.3.3 when SIP is disabled, but not using the newest R v.3.4.2. You can still install R v.3.3.3 from CRAN so it's fine, but I'm wondering what it is about R v.3.4.2 that isn't compatible with GLMr? (I've also tested GLMr v.3.1.10, 3.1.12, and 3.1.13 and none of those versions work either). |
I just tested @akrinos forked version of GLMr and can confirm that it works successfully on a Sierra machine using R v.3.4.2 with SIP enabled. I will test on a machine with R v.3.3.3 tomorrow and let you know. |
Problem with commit to #120 was clearly manipulating exec directory structure; most recent commit rolled back because *nix build issue was not resolved. Search for alternate workable SIP/DYLD solution ongoing. |
It seems restrictions have gotten tighter on macOS Sierra. Having trouble running GLM through GLMr on Sierra. Getting
dyld: Library not loaded
error messages.I have tried altering
Gatekeeper
settings via instructions here. No luck yet. I think it might be an issue with our use ofDYLD_FALLBACK_LIBRARY_PATH
, but I am not 100% certain.Has anyone run into this? Any luck on dealing with this issue?
The text was updated successfully, but these errors were encountered: