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.
>To: address@hidden >From: Harry Edmon <address@hidden> >Subject: Digital Unix 4.0 problem with netcdf 3.3 >Organization: Dept of Atmospheric Sciences, University of Washington >Keywords: 199705291834.MAA11048 Hi Harry, > Using the DEC "cxx" compiler you get the following: > > cxx -c -O -I../libsrc -DNDEBUG netcdf.cc > cxx -c -O -I../libsrc -DNDEBUG ncvalues.cc > cxx: Error: ncvalues.cc, line 156: In this statement, the argument list > "ostrstream(s,sizeof(s))<<the_values[n]" matches no "ostream::operator <<". > as_string_implement(short) > ^ > cxx: Error: ncvalues.cc, line 157: In this statement, the argument list > "ostrstream(s,sizeof(s))<<the_values[n]" matches no "ostream::operator <<". > as_string_implement(nclong) > ^ > cxx: Error: ncvalues.cc, line 158: In this statement, the argument list > "ostrstream(s,sizeof(s))<<the_values[n]" matches no "ostream::operator <<". > as_string_implement(float) > ^ > cxx: Error: ncvalues.cc, line 159: In this statement, the argument list > "ostrstream(s,sizeof(s))<<the_values[n]" matches no "ostream::operator <<". > as_string_implement(double) > ^ > *** Exit 1 > Stop. We don't have DEC's C++ compiler (can't afford it), so we have used g++ on Digital Unix 4.0, which seems to work fine. I'll see if we can get access to an evaluation copy or to another OSF1 4.0 platform with DEC's cxx on it to debug the problem. From the above, it appears to me to be a problem with an incomplete stream implementation. Does the following simple 7-line program compile and run with DEC's cxx, producing "1" as output? #include <iostream.h> int main( void ) { short s = 1; cout << s << '\n'; } If not, I think you should report this as a bug to DEC. --Russ