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.
Oops, forgot to CC: support-netcdf ------- Forwarded Message Date: Thu, 17 Jul 1997 09:33:10 -0600 From: Russ Rew <address@hidden> To: Beiying Wu <address@hidden> Subject: Re: 970717: Problem in installing netcdf >To: address@hidden >From: Beiying Wu <address@hidden> >Subject: Problem in installing netcdf >Organization: UCAR >Keywords: 199707171310.HAA09585 Hi Beiying, > We did what you told us. The following is the feedback. Please help! > I'll mail the second part after this message. > > Beiying Wu > Atmospheric Chemistry Division > National Center for Atmospheric Research > P.O. Box 3000 > Boulder, CO80307 > Tel. 303 497 1449 > Email. address@hidden > > > - ---------- Forwarded message ---------- > Date: Thu, 17 Jul 1997 14:09:29 +0900 (CDT) > From: QIAO Jin-Song <address@hidden> > To: Beiying Wu <address@hidden> > Subject: Re: FTP > > Dear Prof. Wu > > I've got the netcdf-3.3.1 from the address in your E-mail. it built a > library for c. But it didn't find Fortran compiler( because it checked > the command of f77 instead of f90, where we have only f90 in our > machine.) I can change the code to f90 manually. but I find there is a > message that f90 is not compatable with the c89 compiler, I don't know > the reason. In fact, the error message which we have got yesterday is > said it cannot link with the old copiler's object file. Can you ask > someone if it is OK if we install another f77 compiler in the same machine. > > OK, I'll read some more about the INSTALL and README. and try to see if I > can handle this code. > > I'll tell you each step. > > Have LiGuoHui write to you? I told him many times to write to you, to > tell you how much he had done, but he seems not very willing to write mail. > > Joe > > > >From address@hidden Thu Jul 17 07:12:07 1997 > Received: from acd.ucar.edu (acd.ucar.edu [128.117.32.211]) > by unidata.ucar.edu (8.8.6/8.8.6) with ESMTP id HAA09623; > Thu, 17 Jul 1997 07:12:06 -0600 (MDT) > Organization: . > Keywords: 199707171312.HAA09623 > Received: from localhost (beiying@localhost) by acd.ucar.edu (AIX4.2/UCB > 8.7/8.7) with SMTP id HAA19982; Thu, 17 Jul 1997 07:12:06 -0600 (MDT) > Date: Thu, 17 Jul 1997 07:12:05 -0600 (MDT) > From: Beiying Wu <address@hidden> > To: address@hidden, address@hidden > Subject: Build error. (fwd) > Message-ID: <address@hidden> > MIME-Version: 1.0 > Content-Type: MULTIPART/ALTERNATIVE; > BOUNDARY="----=_NextPart_000_01BC92D5.B8142AB0" > Content-ID: <address@hidden> > > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without MIME-aware tools. > Send mail to address@hidden for more info. > > - ------=_NextPart_000_01BC92D5.B8142AB0 > Content-Type: TEXT/PLAIN; CHARSET=gb2312 > Content-ID: <address@hidden> > > > > - ---------- Forwarded message ---------- > Date: Thu, 17 Jul 1997 17:20:27 -0000 > From: Qiao Jinsong <address@hidden> > To: address@hidden > Subject: Build error. > > Dear Prof. Wu > I have tried to make the netcdf-3.3.1. after changing some flags, it could > build a library. but I met a error now. It's because it could not find some > functions which will be used in some files. I don't know if it is the > functions of netcdf( which mean the netcdf's library is not linked) or some > other library. I have put the "make"'s output message in the following > paragraphs. Could you find someone to explain what I have done, and what I > still need to do. I think maybe the netcdf library is OK now. > Joe > > Making `all' in directory /usr/people/joe/netcdf-3.3.1/src/libsrc > > /bin/cc -n32 -c -O -I. -DNDEBUG attr.c > /bin/cc -n32 -c -O -I. -DNDEBUG dim.c > /bin/cc -n32 -c -O -I. -DNDEBUG error.c > /bin/cc -n32 -c -O -I. -DNDEBUG -DVERSION=`cat ../VERSION` libvers.c > /bin/cc -n32 -c -O -I. -DNDEBUG nc.c > /bin/cc -n32 -c -O -I. -DNDEBUG ncio.c > /bin/cc -n32 -c -O -I. -DNDEBUG ncx.c > /bin/cc -n32 -c -O -I. -DNDEBUG putget.c > /bin/cc -n32 -c -O -I. -DNDEBUG string.c > /bin/cc -n32 -c -O -I. -DNDEBUG v1hpg.c > /bin/cc -n32 -c -O -I. -DNDEBUG v2i.c > /bin/cc -n32 -c -O -I. -DNDEBUG var.c > ar cru libnetcdf.a attr.o dim.o error.o libvers.o nc.o ncio.o > ncx.o putget.o string.o v1hpg.o v2i.o var.o > : libnetcdf.a > > Returning to directory /usr/people/joe/netcdf-3.3.1/src > > > Making `all' in directory /usr/people/joe/netcdf-3.3.1/src/fortran > > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-attio.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-control.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-dim.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-genatt.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-geninq.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-genvar.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-lib.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-misc.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-v2compat.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-vario.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-var1io.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-varaio.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-varmio.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG fort-varsio.c > ar cru ../libsrc/libnetcdf.a fort-attio.o fort-control.o > fort-dim.o fort-genatt.o fort-geninq.o fort-genvar.o fort-lib.o > fort-misc.o fort-v2compat.o fort-vario.o fort-var1io.o > fort-varaio.o fort-varmio.o fort-varsio.o > : ../libsrc/libnetcdf.a > > Returning to directory /usr/people/joe/netcdf-3.3.1/src > > > Making `all' in directory /usr/people/joe/netcdf-3.3.1/src/ncdump > > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG ncdump.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG vardata.c > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG dumplib.c > /bin/cc -n32 -o ncdump -O ncdump.o vardata.o dumplib.o -L../libsrc > -lnetcdf > > Returning to directory /usr/people/joe/netcdf-3.3.1/src > > > Making `all' in directory /usr/people/joe/netcdf-3.3.1/src/ncgen > > /bin/cc -n32 -c -O -I../libsrc -I. -DNDEBUG main.c > /bin/cc -n32 -c -O -I../libsrc -I. -DNDEBUG load.c > /bin/cc -n32 -c -O -I../libsrc -I. -DNDEBUG ncgentab.c > /bin/cc -n32 -c -O -I../libsrc -I. -DNDEBUG escapes.c > /bin/cc -n32 -c -O -I../libsrc -I. -DNDEBUG getfill.c > /bin/cc -n32 -c -O -I../libsrc -I. -DNDEBUG init.c > /bin/cc -n32 -c -O -I../libsrc -I. -DNDEBUG genlib.c > /bin/cc -n32 -o ncgen -O main.o load.o ncgentab.o escapes.o getfill.o > init.o genlib.o ../libsrc/libnetcdf.a > > Returning to directory /usr/people/joe/netcdf-3.3.1/src > > > Making `all' in directory /usr/people/joe/netcdf-3.3.1/src/cxx > > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG netcdf.cc > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG ncvalues.cc > ar cru libnetcdf_c++.a netcdf.o ncvalues.o > : libnetcdf_c++.a > /bin/cc -n32 -c -O -I../libsrc -DNDEBUG nctst.cc > /bin/cc -n32 -o nctst -I../libsrc -DNDEBUG -O nctst.o > libnetcdf_c++.a -L../libsrc -lnetcdf > > "/usr/ccs/bin/yaccpar", line 5: warning(1155): unrecognized #pragma > #pragma ident "@(#)yaccpar 6.12 93/06/07 SMI" > ^ > > ld32: ERROR 33: Unresolved text symbol "__ls__7ostreamGPCc" -- 1st referenced > by nctst.o. > ld32: ERROR 33: Unresolved text symbol "__ct__13Iostream_initGv" -- 1st > referenced by nctst.o. > ld32: ERROR 33: Unresolved text symbol "__record_needed_destruction" -- 1st > referenced by nctst.o. The above just indicates a failure of /bin/cc (a C compiler) to properly link compiled C++ code. Set the CXX environment variable to "" (to indicate you don't want the C++ interface built) or to a C++ compiler on your IRIX system, for example /bin/CC (not the same as /bin/cc). The above output from make also indicates you are not compiling and building the Fortran interface, perhaps because you set the environment variable FC="" before running the "configure" script. Our INSTALL document indicates various combinations of C and Fortran compilers that we have tested on various versions of IRIX: IRIX 5.3 /bin/cc /bin/f77 IRIX 6.2 /bin/cc /bin/f77 IRIX 6.2 /bin/cc /bin/f90 IRIX 6.2 /bin/c89 /bin/f77 IRIX 6.2 /bin/c89 -n32 /bin/f77 -n32 IRIX64 6.2 /bin/cc /bin/f77 IRIX64 6.2 /bin/cc -64 /bin/f77 -64 If you have some other version of IRIX or are trying some other combination of compilers and compiler flags that we haven't tested, there may be a problem. If you still can't build this package, then please send a description of the problem together with the following to <address@hidden>: 1. The standard output of the command "uname -a" 2. The contents of the file VERSION, which is in the top-level source directory 3. The standard output and error output of the configure script 4. The absolute pathnames of all compilers (C, FORTRAN, C++) used in the build process (use the type(1) or which(1) utility to determine this) 5. The contents of the file "config.log", which is in the top-level source directory 6. The standard output and error output of the command "make" 7. The standard output and error output of the command "make test" Thanks. - --Russ _____________________________________________________________________ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu ------- End of Forwarded Message