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

970522: Netcdf3.3 build trouble

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: 970522: Netcdf3.3 build trouble
  • Date: Thu, 22 May 97 08:29:24 -0600
Dear Eek Hyun Cho,

>Date: Thu, 22 May 1997 16:02:51 +0900 
>From: Eek Hyun Cho <address@hidden>
>Organization: Atmospheric Sciences 
>To: Steve Emmerson <address@hidden>
>Subject: Re: 970521: Netcdf3.3 build trouble 
>Keywords: 199705210701.BAA18722

In the above message, you wrote:

> > I'm sorry, but I don't understand what you mean.  Did you not try to
> > execute the "make" command?  Did you try, but it failed for some reason
> > (if so, what was the reason).  Would you please explain what you mean in
> > more detail.

> After configure process, I typed 'make all' and hit enter key, but
> don't excuted.  (Error massage in shell prompt is 'make command not
> found')

Ah!  It appears that the problem has nothing to do with the netCDF
3.3 distribution, but rather that the directory that contains the
make(1) utility is not in your PATH environment variable.  On my
SunOS 5.5 system, the make(1) utility is contained in the directory
"/usr/ccs/bin"; therefore, I have that directory in my PATH environment
variable.  For example:

    $ echo $PATH
    /opt/SUNWspro/bin:/opt/bin:/bin:/usr/bin:/usr/ccs/bin:/usr/local/bin

See your shell's manual page or a local UNIX expert for more information
on the PATH environment variable.

I suggest that you add the relevant directory to your PATH environment
variable and try the "make" again.

> I think conftest.c file is failed for configure process.
> (after line 2539 in config.log)

The file "config.log" contains error messages from the configure script
and the utilities that it invokes during its examination of your system.
This examination is expected to generate errors.  The error you refer to
can safely be ignored.

--------
Steve Emmerson   <address@hidden>