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

Re: 19990831: netcdf-3.4 installation make fails on IBM RS/6000

Harsh,

>Date: Tue, 31 Aug 1999 09:49:17 -0700
>From: Harsh Anand <address@hidden>
>Organization: LBNL/NERSC
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19990831: netcdf-3.4 installation make fails on IBM RS/6000
>Keywords: 199908302133.PAA20130

In the above message, you wrote:

> make fails again.
> 
> Here are the environment variables I set before I run configure:
> 
> setenv CC       xlc
> setenv CPPFLAGS "-D_ALL_SOURCE -DNDEBUG  -D_XOPEN_SOURCE"
> setenv CFLAGS   -O
> setenv FC       xlf
> setenv FFLAGS   -O
> setenv CXX      KCC
> setenv LIBS     "-L /lib -lm"
> 
> ********************************************
...
> Making `all' in directory /usr/common/usg/netcdf/3.4/src/cxx

Well, this is a lot further than before.

> 
> make[2]: Entering directory `/usr/common/usg/netcdf/3.4/src/cxx'
> KCC -c -O  -I../libsrc  -D_ALL_SOURCE -DNDEBUG  -D_XOPEN_SOURCE netcdf.cc
> "ncvalues.hh", line 40: warning: integer conversion resulted in a change of
>           sign
>   static const ncbyte ncBad_byte = NC_FILL_BYTE;
>                                    ^
> 
> KCC -c -O  -I../libsrc  -D_ALL_SOURCE -DNDEBUG  -D_XOPEN_SOURCE ncvalues.cc
> "ncvalues.hh", line 40: warning: integer conversion resulted in a change of
>           sign
>   static const ncbyte ncBad_byte = NC_FILL_BYTE;
>                                    ^
> 
> ar cru   libnetcdf_c++.a netcdf.o ncvalues.o
> ranlib libnetcdf_c++.a
> KCC -c -O  -I../libsrc  -D_ALL_SOURCE -DNDEBUG  -D_XOPEN_SOURCE nctst.cc
> "ncvalues.hh", line 40: warning: integer conversion resulted in a change of
>           sign
>   static const ncbyte ncBad_byte = NC_FILL_BYTE;

I wouldn't worry about the above.  If they're serious, then the "make
test" will tell you.

> "nctst.cc", line 19: error: expected an identifier
>       const int TIMELEN = 20;
>                 ^

Hmm...  I hate to say it, but the above looks like a bug in your C++
compiler, KCC.  Do you need the C++ interface and, if so, do you need to
use KCC?

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