[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #CCG-157720]: Netcdf4-fortran-4.5.3 Error



Hello,

What platform are you trying to build on? This is an interesting error, as it 
is complaining about a missing system library, but if the system library were 
truly missing, it would not have reached the point of running tests.  Would it 
be possible to get the config.log file generated when you ran 'configure' to 
build netcdf fortran?

Thanks,

-Ward

> I am trying to install netcdf so that I can compile and run WRF. I was 
> following the online guide for installation 
> (https://www.unidata.ucar.edu/software/netcdf/docs/building_netcdf_fortran.html
>  
> <https://www.unidata.ucar.edu/software/netcdf/docs/building_netcdf_fortran.html>)
>  starting by setting up the netcdf-c installation first. I was able to get 
> that running successfully, however when running make check for the 
> netcdf-fortran version, I receive the following error (in the test-suite.log 
> file):
> 
> dyld: Library not loaded: @rpath/libgfortran.3.dylib
> Referenced from: 
> /Users/misi1684/Downloads/netcdf-fortran-4.5.3/nf_test/.libs/nf_test
> Reason: image not found
> FAIL nf_test (exit status: 134)
> 
> I tried a couple of online resources to trouble shoot, but none seemed to 
> work. After running make check command, the printed failure states to contact 
> this email. Resources I have used to trouble shoot: 
> https://wusun.name/blog/2018-04-27-conda-libgfortran-issue/ 
> <https://wusun.name/blog/2018-04-27-conda-libgfortran-issue/> , 
> https://github.com/numpy/numpy/issues/12970 
> <https://github.com/numpy/numpy/issues/12970> , and 
> https://github.com/conda/conda/issues/5279 
> <https://github.com/conda/conda/issues/5279> .
> Let me know if you need any other documentation to diagnose this issue!
> 
> Michaela
> 


Ticket Details
===================
Ticket ID: CCG-157720
Department: Support netCDF
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.