This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Matthew, I notice that the latest version (2.4) of the Mac OS X Developer Tools (available for download from the Apple Developer Connection, developer.apple.com, free to registered developers) adds support for 64-bit Intel based Mac computers. I'm just trying to set up a testing environment that will use Developer Tools 2.4.1 and the latest versions of g95 and gfortran from fink (fink.sourceforge.net) to see if we can reproduce problems with building from source on Intel Mac OS X platforms. Currently all our testing is on a PowerPC G5 platfrom, where things works fine with either g95 or gfortran. I'm surprised if you built the netCDF library, libnetcdf.a, from source on an Intel platform and you got a ppc library. Did you run "make install" to make sure the new library was installed where you had specified with the "--prefix" argument to the configure script? If not, can you try linking with netcdf-3.6.1/src/libsrc/libnetcdf.a in the source directory instead of whatever is in /usr/lib/libnetcdf.a? If the library in the source directory is a ppc library, something is very wrong. Until we get our Intel MacOSX development and testing environment set up here (which may be a few days), you might also check where the g77 and g95 you have came from, and that they are compatible with the version of Mac OS X and Intel platform you are using. It's possible you might have to build and install g77 and g95 from source. When you run the netCDF "configure" script it attempts to compile with the Fortran compilers it finds, and it would also be helpful to look at the output of running "configure", after you have run "make clean". If that indicates problems you can't diagnose, it would be helpful to supply the information requested in the "Reporting Problems" link on the netCDF home page: http://www.unidata.ucar.edu/software/netcdf/docs/netcdf-install/Reporting-Problems.html#Reporting-Problems --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: FEZ-604468 Department: Support netCDF Priority: Normal Status: Closed