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

Re: 19990310: Trying to install NetCDF under Sun OS 5.6

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: Re: 19990310: Trying to install NetCDF under Sun OS 5.6
  • Date: Wed, 10 Mar 1999 15:23:38 -0700
Tom,

>Date: Wed, 10 Mar 1999 17:09:32 -0500
>From: "Parr, J. Tom" <address@hidden>
>Organization: TASC
>To: "'Steve Emmerson'" <address@hidden>
>Subject: RE: 19990310: Trying to install NetCDF under Sun OS 5.6 
>Keywords: 199903101840.LAA17723

In the above message, you wrote:

...
> Content-Disposition: attachment;
>       filename="configure.log"
> 
> configure: warning: /usr/local/sp/NetCDF/lib: invalid host type=0A=
> creating cache ./config.cache=0A=
> checking for m4... no=0A=
> checking for gm4... no=0A=
> checking user-defined C compiler =
> "/usr/local/lang/opt/SUNWspro/bin/c89"=0A=
> checking C compiler... works=0A=
> checking how to make dependencies... cc -xM=0A=
> checking for CC... CC=0A=
> checking C++ compiler "CC"... works=0A=
> checking how to run the C preprocessor... =
> /usr/local/lang/opt/SUNWspro/bin/c89 -E=0A=
> checking user-defined Fortran compiler =
> "/usr/local/lang/opt/SUNWspro/bin/f77"... works=0A=
> checking for Fortran .F compiler... =0A=
> checking if Fortran compiler handles *.F files... yes=0A=
> checking for C-equivalent to Fortran routine "SUB"... configure: nm: =
> not found=0A=
...

[ASIDE: What's with all the "=0A="s in the above?]

The above error indicates that the configure script couldn't find the
"nm" utility.  On your system, this utility should be located in the
"/usr/xpg4/bin" or "/usr/ccs/bin" directory.  Find the utility and add
the parent directory to your PATH environment variable.

When you've done that, then execute steps 2 through 9 near the end of
the INSTALL file.

Please let me know if this helps.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>