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.
Aaron, >Date: Fri, 16 Aug 1996 16:41:06 -0600 >From: address@hidden (Aaron Lai) >Organization: Los Alamos National Laboratory >To: address@hidden >Subject: Re: 960816: netCDF xdr_ link >Keywords: 199608162049.AA25923 In the above message you wrote: > ... Thus, a link-command should be > something like the following: > > ld ... -L/usr/local//lib -lnetcdf ... -lnsl > > The `-lnsl' argument references the network support library. > > --------------- > > Do you mean that I should change the 'configure' or 'Makefile' or > 'CUSTOMIZE' files? Or, do I just insert the 'ld' when I compile the > program 'gennet.for'? > > I don't have much knowledge about 'Makefile'. You shouldn't change the makefiles in the netCDF package. They already know about referencing the Solaris network support library when they build the utilities ncgen(1), and ncdump(1). You must, however, change the makefiles in any other package that you build that uses the netCDF library. Each linking of a netCDF-using program should contain the argument `-lnsl'. For forther information, see the manual pages on the cc(1), ld(1), and make(1) utilities. Please let me know if this helps. -------- Steve Emmerson <address@hidden>