Replies: 9 comments 9 replies
-
I ran into similar issue with a MacPro M2 However, the folder has libgfortran.5.dylib rather than libgfortran.4.dylib So, maybe need to install older version of gcc to get the ncl working |
Beta Was this translation helpful? Give feedback.
-
Any updates on these issues? I have tried installing NCL with brew, macports, and conda, but all with different error messages (with Macbook Pro, M2 Pro). Thank you! |
Beta Was this translation helpful? Give feedback.
-
This is an upstream bug where the precompiled binaries upstream provides depend on an x86 GFortran install. This should be reported and fixed upstream, the comment about multiple install methods having this issue is a very clear indication that this isn't a new issue. |
Beta Was this translation helpful? Give feedback.
-
Hi to all, are there any updates on the issue? I tried installing with miniconda. I think the errors are persisting. |
Beta Was this translation helpful? Give feedback.
-
Manually download an early version of gcc from https://hpc.sourceforge.net/, for example, gcc-7.3. |
Beta Was this translation helpful? Give feedback.
-
related to MITgcm/MITgcm#846 ? |
Beta Was this translation helpful? Give feedback.
-
I am also having problems getting ncar-ncl to work on an M3 MacBook Pro running Sonoma (14.5). I tried initially with anaconda, following the recommended method from the ncl page. That does not work for me. Either the executable is not installed, or it cannot be found. The command 'ncl' or 'ncl -V' returns 'command not found'. So now I am trying to use brew to install. brew install --cask ncar-ncl For bash shell, add these lines to ~/.bash_profile: export NCARG_ROOT="/opt/homebrew/ncl-6.6.2" You may also need to modify your DYLD_FALLBACK_LIBRARY_PATH export DYLD_FALLBACK_LIBRARY_PATH=$(dirname $(gfortran --print-file-name libgfortran.3.dylib)):$DYLD_FALLBACK_LIBRARY_PATH` I then followed the recommendation to add the two lines of code to ~/.bash_profile. ncl does not work. Nothing happens upon trying to open it. So then I modified
What now? I have wasted a large amount of time on this. |
Beta Was this translation helpful? Give feedback.
-
… On Tue, Nov 12, 2024 at 1:54 AM levi silvers ***@***.***> wrote:
I am also having problems getting ncar-ncl to work on an M3 MacBook Pro
running Sonoma (14.5). I tried initially with anaconda, following the
recommended method from the ncl page. That does not work for me. Either the
executable is not installed, or it cannot be found. The command 'ncl' or
'ncl -V' returns 'command not found'.
So now I am trying to use brew to install.
brew install --cask ncar-ncl
==> Auto-updating Homebrew... Adjust how often this is run with
HOMEBREW_AUTO_UPDATE_SECS or disable with HOMEBREW_NO_AUTO_UPDATE. Hide
these hints with HOMEBREW_NO_ENV_HINTS (see man brew). ==> Downloading
https://ghcr.io/v2/homebrew/portable-ruby/portable-ruby/blobs/sha256:303bed4c7fc431a685db3c3c151d873740114adbdccd23762ea2d1e39ea78f47
#########################################################################
100.0% ==> Pouring portable-ruby-3.3.6.arm64_big_sur.bottle.tar.gz ==>
Auto-updated Homebrew!
.
.
.
`==> Installing Cask ncar-ncl
==> Moving Generic Artifact 'include' to '/opt/homebrew/ncl-6.6.2/include'
==> Moving Generic Artifact 'bin' to '/opt/homebrew/ncl-6.6.2/bin'
==> Moving Generic Artifact 'lib' to '/opt/homebrew/ncl-6.6.2/lib'
🍺 ncar-ncl was successfully installed!
==> Caveats
==> ncar-ncl
To use ncar-ncl, you must add the ${NCARG_ROOT}/bin directory
to your PATH environment variable.
For bash shell, add these lines to ~/.bash_profile:
export NCARG_ROOT="/opt/homebrew/ncl-6.6.2"
export PATH="${NCARG_ROOT}/bin:${PATH}"
You may also need to modify your DYLD_FALLBACK_LIBRARY_PATH
environment variable:
export DYLD_FALLBACK_LIBRARY_PATH=$(dirname $(gfortran --print-file-name
libgfortran.3.dylib)):$DYLD_FALLBACK_LIBRARY_PATH`
I then followed the recommendation to add the two lines of code to
~/.bash_profile. ncl does not work. Nothing happens upon trying to open it.
So then I modified DYLD_FALLBACK_LIBRARY_PATH as recommended. Now, when
trying to open/run ncl, apparently my system can find ncl but I get a pop
up window stating that
"ncl" cannot be opened because the developer cannot be verified. macOS
cannot verify that this app is free from malware.
What now? I have wasted a large amount of time on this.
—
Reply to this email directly, view it on GitHub
<#3573 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRADARWNYNX7UZ6RFOEW7L2AFGVDAVCNFSM57WM3Y42U5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCMJSGIYDCMBW>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Ok, as an update. Once I allowed my Mac to open up the ncl package from homebrew, then I ended up with the gfortran that others on this thread mentioned. I downloaded gcc-7.3 from https://hpc.sourceforge.net/ and untarred the package. I was running into permission errors when trying to locate it in /usr/opt/ or /opt/homebrew/. If I untarr in a location for which I have permission and then add an appropriate DYLD_FALLBACK_LIBRARY_PATH definition in my .bash_profile file ncl seems to be working. However, this is only after my Mac not wanting to open numerous (~10) packages within the gcc-7.3 package and me overriding the safety recommendations. Thanks for your help! Especially luoxiao11! |
Beta Was this translation helpful? Give feedback.
-
Hi,
I installed NCL (NCAR software) using this formulae:
It ran with no issues. My brew was/is updated. However, when I type ncl in the terminal I get the following error:
I am using a MacPro M1 chip. OSX 12.5.1 updated
The command
env | grep NCARG
gives the following output:NCARG_ROOT=/opt/homebrew/ncl-6.6.2
Could someone be so kind to give me a hint why is this happeing? Why the libgfortran.4.dylib is not available in my system?
which gfortran
/opt/homebrew/bin/gfortran
gfortran -v
Using built-in specs.
Thanks for any hint.
Luis
Beta Was this translation helpful? Give feedback.
All reactions