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

[netCDF #ZDY-666039]: NETCDF build with open64 compiler


> Thanks for your reply. I've created a simple HOWTO build NetCDF with open64 
> compiler page. It is accessible at following url,
> http://developer.amd.com/cpu/open64/AppsAndLibraries/Documents/building_netcdf.html
> If you could add this info. On NetCDF site, that will be great.

I have one request, if it's not too much trouble.  When it's convenient, could 
you try using the
latest stable netCDF release, version 4.1.1, instead of 4.0?  We have made many 
in the software since version 4.0 was released in June 2008, and we would 
rather users get a
more current release, 4.1.1 from May 2010.  The 4.1.1 release should be just as 
easy or easier 
to build, and we would get fewer support questions about bugs we have already 
fixed.  The 
4.1.1 release (or the latest current stable release) is available from


or from the download link on the netCDF home page at




> -----Original Message-----
> From: Unidata netCDF Support [mailto:address@hidden
> Sent: Wednesday, October 06, 2010 9:59 AM
> To: Pawar, Uttam
> Cc: address@hidden
> Subject: [netCDF #ZDY-666039]: NETCDF build with open64 compiler
> Hi Uttam,
> > My name is Uttam Pawar. I'm an engineer at AMD, working on improving
> > open64 compiler tool chain. As part of measuring competitiveness, we have
> > been building few scientific applications with this tool chain, one of
> > them is NETCDF (used for POP). As I've noticed on your website, quite a
> > few compilers are mentioned and I would like to know if I can contribute
> > the binary release of NETCDF built with open64 compiler tool chain. If
> > it's ok to submit binaries, then I would like to know things involved
> > in making useful and successful NETCDF build which can be released.
> Thanks, it's very generous of you to offer to make the results of your
> work available!  Unfortunately, for security reasons, we can't
> distribute binaries we don't build here.  Also, there are so many
> development environments avaiable now that we are intending to rely on
> package maintainers for packaging systems such as rpm, dpkg, opencsw,
> fink, etc. to make netCDF available for specific compilers, including
> all dependencies such as for hdf5 and libcurl.
> What would be helpful is if you could provide the URL of a web site
> that provides notes on building netCDF with your compiler, such as are
> provided for PGI and Intel compilers at:
> http://www.pgroup.com/resources/tips.htm#NETCDF
> http://software.intel.com/en-us/articles/performance-tools-for-software-developers-building-netcdf-with-the-intel-compilers/
> Alternatively, you could provide us with tips or settings that work
> especially well with your compilers, and we could include them as an
> entry in our web page on "Other Builds of the netCDF Package" at
> http://www.unidata.ucar.edu/netcdf/docs/other-builds.html
> > I really appreciate any help in this matter.
> Thanks for using netCDF for testing your compilers!  If you would like
> to test on the upcoming version 4.1.2-beta2 or the current snapshot
> release at
> ftp://ftp.unidata.ucar.edu/pub/netcdf/snapshot/netcdf-4-daily.tar.gz
> we would be interested in fixing any problems you report on
> portability of the code to your compilers.
> --Russ
> Russ Rew                                         UCAR Unidata Program
> address@hidden                      http://www.unidata.ucar.edu
> Ticket Details
> ===================
> Ticket ID: ZDY-666039
> Department: Support netCDF
> Priority: High
> Status: Closed

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu

Ticket Details
Ticket ID: ZDY-666039
Department: Support netCDF
Priority: High
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.