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

Re: [Jim Young: Re: netcdf and compilers ]

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: [Jim Young: Re: netcdf and compilers ]
  • Date: Thu, 28 Apr 1994 11:35:47 -0600
>From: Jim Young <address@hidden>
>Organization: .
>Keywords: 199404262227.AA05254
>Date: Tue, 26 Apr 1994 18:26:59 -0400 (EDT)
>Subject: Re: netcdf and compilers 

Jim,

re:
>On Fri, 15 Apr 1994, Russ Rew wrote:
>> To get this C run-time library, you will have to have installed a C
>> compiler, for example Microsoft C.  With Microsoft C, the name of the
>> run-time C library file is LLIBCE.LIB, with Borland C it probably has a
>> different name.
>
>I have obtained Microsoft C v.51 (compatible with Microsoft Fortran v.41)
>and have again tried to compile the sample fortran program on the PC. Once
>again the compile stage produces "length & type" mismatch errors.  At the
>link stage the following errors have been logged. The netcdf and xdr
>libraries were obtained from the ftp site. Sorry if these seem like stupid
>questions but I have been working at this (reading docs & notes) for days 
>and nothing I have tried seems to work. 

Please note that we have tested the netCDF package on MS DOS using Microsoft
C 6.0 and Microsoft Fortran 5.1.

>Microsoft (R) Segmented-Executable Linker  Version 5.01.21
>Copyright (C) Microsoft Corp 1984-1988.  All rights reserved.
>
>Object Modules [.OBJ]: JIM.OBJ+C:\NETCDF\FSLEN.OBJ+C:\NETCDF\JACKETS.OBJ
>Run File [JIM.EXE]: 
>List File [NUL.MAP]: 
>Libraries [.LIB]: C:\FORV41\LIB\LLIBFORE.LIB+C:\CV51\LIB\LLIBCE.LIB+C:\NETCDF\
> XDR.LIB+C:\NETCDF\NETCDF.LIB;
>
>LINK : error L2029: Unresolved externals:
>
>__aFchkstk in file(s):
>C:\NETCDF\XDR.LIB(byteordr.c) C:\NETCDF\XDR.LIB(xdrfloat.c)
>C:\NETCDF\XDR.LIB(xdr.c) C:\NETCDF\NETCDF.LIB(xdrposix.c)
>C:\NETCDF\NETCDF.LIB(string.c) C:\NETCDF\NETCDF.LIB(sharray.c)
>C:\NETCDF\NETCDF.LIB(iarray.c) C:\NETCDF\NETCDF.LIB(var.c)
>C:\NETCDF\NETCDF.LIB(putget.c) C:\NETCDF\NETCDF.LIB(file.c)
>C:\NETCDF\NETCDF.LIB(error.c) C:\NETCDF\NETCDF.LIB(dim.c)
>C:\NETCDF\NETCDF.LIB(cdf.c) C:\NETCDF\NETCDF.LIB(attr.c)
>C:\NETCDF\NETCDF.LIB(array.c) C:\NETCDF\JACKETS.OBJ(jackets.c)
>
> __FF_DBGMSG in file(s): 
> C:\FORV41\LIB\LLIBFORE.LIB(../_puterr.c)
>
>There were 2 errors detected
>
>    __________________________________________________________

The first unresolved external is a result of how your Fortran and/or C libraries
were built.  I can't recall right off (it should be in the installation
notes) whether you need to specify C compatibility or no C compatibility
when the library is built.  I suggest you try building the C library with
no Fortran compatibility and the Fortran with C compatibility.  I will
review this problem in more detail in a few days as I get time and get
back to you.
--
Tom Yoksas                                 address@hidden
Unidata User Support                       (303) 497-8642  (last resort)