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

961217: netCDF Build, almost done!

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: 961217: netCDF Build, almost done!
  • Date: Tue, 17 Dec 96 17:02:18 -0700
Steve,

>Date: Tue, 17 Dec 1996 17:23:37 -0500 (EST) 
>From: Steve Johns <address@hidden>
>To: address@hidden (Steve Emmerson)
>Subject: Re: 961217: netCDF Build, almost done! 

In the above message you wrote:

> Yes.  Thanks much.  After unsetenv LIBS, configure ran fine, as did
> most of the compile.  It quit in the cxx directory:

> make/disk3/people/mddevel/netcdf-2.4.3/src/cxx>make
> ar rcuv libnetcdf_c++.a netcdf.o ncvalues.o
> case "" in \
> '') ;; \
> *)  ar rucv libnetcdf_c++.a ;; \
> esac
> ranlib libnetcdf_c++.a
> CC  nctst.o -L. -lnetcdf_c++ -L../libsrc -lnetcdf  -o nctst
> ld:
> Unresolved:
> strlen(const char*)
> strncpy(char*,const char*,unsigned int)
> strcpy(char*,const char*)
> strcmp(const char*,const char*)
> make: *** [nctst] Error 1
> 
> 
> This is strings.h stuff, isn't it?

Yes, it is.  I'm surprised your C++ compiler isn't finding the C runtime.
(Ours does).

I'm afraid you'll have to experiment with the above command line to see
what is necessary to get it to work (e.g. what C runtime library reference
is needed).

--------
Steve Emmerson   <address@hidden>