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

Re: 980629: compilation error; Linux: iostream.h not found

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: 980629: compilation error; Linux: iostream.h not found
  • Date: Mon, 29 Jun 1998 12:46:18 -0600
Tim,

In the above message, you wrote:

> To: address@hidden
> From: address@hidden
> Subject: compilation error; Linux
> Organization: .
> Keywords: 199806291623.KAA19742

In the above message you wrote:

> I'm getting the error
> 
> In file included from netcdf.hh:16,
>                  from netcdf.cc:12:
> ncvalues.hh:13: iostream.h: No such file or directory
> ncvalues.hh:17: strstream.h: No such file or directory
> make[2]: *** [netcdf.o] Error 1
> make[2]: Leaving directory `/home/dowling/epic/netcdf/netcdf-3.4/src/cxx'
> make[1]: *** [subdir_target] Error 1
> make[1]: Leaving directory `/home/dowling/epic/netcdf/netcdf-3.4/src'
> make: *** [cxx/install] Error 2
> 
> I'm trying to use g77, and I set environment variables according
> to the "Linux using g77" note from Phil Austin and Jan Polcher.
> 
> Here's all my info in the order you specified:
> 
> p.s.  Once I get this working, please add the Explicit Planetary Isentropic
> Coordinate (EPIC) Atmospheric Model to the list of happy users of netCDF
> (available at the NASA Planetary Data System (PDS) Atmospheres Node).
> 
> Sincerely,
> 
> Tim Dowling
> 
> -------------------
> 
> matins%pwd
> /home/dowling/epic/netcdf/netcdf-3.4/src
> 
> matins%uname -a
> Linux matins.spd.louisville.edu 2.0.32 #1 Sun Dec 14 17:19:30 EST 1997 i686 
> unknown
> 
> matins%more VERSION
> 3.4
> 
> matins%which cc
> /usr/bin/cc
> matins%which g77
> /usr/local/bin/g77
> matins%which c++
> /usr/local/bin/c++

Hmm...  I don't like the fact that your C compiler is in "/usr/bin" but
your C++ compiler is in "/usr/local/bin" because, in an integrated
environment, they should be in the same place (they are on our Linux
system).  A problem with the compilation environment (e.g. a bad
installation) would be consistent with the problem you encountered.

What are all the C and C++ compilers that you have?

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