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.
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.
Thank you. I will follow that advice. Cheers. -------------- John Helly, UCSD / San Diego Supercomputer Center / Scripps Institution of Oceanography, Climate, Atmospheric Science, and Physical Oceanography / +01 760 840 8660 mobile / stonesteps (Skype) / stonesteps7 (iChat) / /www.sdsc.edu/~hellyj On Oct 19, 2010, at 12:03 PM, Ed Hartnett wrote: Larry Baker <baker@xxxxxxxx> writes: > The reason I put the -m64 in the CC, CXX, and FC variables is so that > - > m64 is supplied to any LD step. That way the 64-bit libraries are > used at link time. This is necessary on some of the platforms I've > used. I think of -m64 as fundamentally selecting a different > compiler; it's not really the same as other compile-time flags. > > Larry Baker > US Geological Survey > 650-329-5608 > baker@xxxxxxxx > Correct! I should also have added: LDFLAGS=-m64 If you look at the netCDF build page, you will see a bunch of platforms, and the environment variables used to build there: http://www.unidata.ucar.edu/software/netcdf/builds/4_1_1/index.jsp (You must log in to Unidata's web site to see this page.) Thanks, Ed -- Ed Hartnett -- ed@xxxxxxxxxxxxxxxx _______________________________________________ netcdfgroup mailing list netcdfgroup@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
netcdfgroup archives: