NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Neil, > To: address@hidden > From: "Neil R. Smith" <address@hidden> > Subject: building 32 $ 64 bin libraries > Organization: Texas A&M University > Keywords: 200007271756.e6RHuMT24673 The above message contained the following: > Hi. This is a netcdf package library problem but I wonder if, > as programers, you know the answer: > > I have built netcdf for our unidata stuff on our Origin 2000 > with -o32 libraries. Since that build and install, we have > a need to build another program, in fact the NCAR CCM model, > which on this 64bit platform, is expecting 64bit netcdf libraries. > > Is there a way to have and make use of both 32bit and 64bit > versions of the netcdf libraries? Or put another way, is there > a way to have both the upc packages and this 64bit model requiring > 64bit libnetcdf ? Do I rebuild the upc packages with 64bit? > > Thanks, -Neil > -- > Neil R. Smith, Comp. Sys. Mngr. address@hidden > Dept. Atmospheric Sci., Texas A&M Univ. 979/845-6272 FAX:979/862-4466 You'll have to build and install the netCDF library twice: once as a 32-bit library and again as a 64-bit library. Make sure you do a "make distclean" between builds. When you build the 64-bit version, ensure that the relevant compilation environment variables have the appropriate 64-bit options. When the first library is installed, rename it appropriately (e.g. "libnetcdf32.a"). Do the same with the second library (e.g. "libnetcdf64.a"). Make sure your programs reference the correct library. Regards, Steve Emmerson <http://www.unidata.ucar.edu>