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

[netCDF #CNY-738623]: Problems installing Netcdf-3.6.1 on MacOSX

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.

  • Subject: [netCDF #CNY-738623]: Problems installing Netcdf-3.6.1 on MacOSX
  • Date: Fri, 12 Jan 2007 15:42:10 -0700
Hi Michael,

What version of MacOS X do you have?  (Check "About This Mac" under the Apple 
menu.)

What are the first few lines of the "configure" script you are trying to run?  
You can use the "head" command to see tthe first ten lines in a terminal 
window.  For the netCDF-3.6.1 release, I get:

$ head configure
#! /bin/sh
# From configure.in Id: configure.in.
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.59 for netCDF 3.6.1.
#
# Report bugs to <address@hidden>.
#
# Copyright (C) 2003 Free Software Foundation, Inc.
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and modify it.

which indicates that /bin/sh is used to execute the script.

When I run the configure script from a terminal window in the netcdf-3.6.1/src 
directory on a Mac OS X machine, it seems to work fine:

$ ./configure
configure: netCDF 3.6.1
checking build system type... powerpc-apple-darwin8.8.0
checking host system type... powerpc-apple-darwin8.8.0
checking whether configure should try to set compiler flags... yes
checking whether netCDF is to be built in 64-bit mode... no
checking where to put large files... .
checking for top-level source-directory... 
/Users/russ/test/nc361/netcdf-3.6.1/src
checking for pathcc... no
checking for xlc... no
checking for icc... no
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
 ...

and so on.  I have the Developers Tools installed on this Mac OS X platform, 
which include the compiler, the "make" tool, and other tools needed for 
development.  If you didn't get a CD or DVD with the Developers Tools (these 
may be called Xcode Development Tools) with your Mac, you can download them for 
free from the Apple Developers site:

  http://developer.apple.com/

--Russ


  


Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: CNY-738623
Department: Support netCDF
Priority: Critical
Status: Closed