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.
> I think this may be caused by an out of date libtool. Anyways, the binaries > don't need to define an rpath of /usr/lib64 because that is the standard path. > > netcdf.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/nccopy ['/usr/lib64'] > netcdf.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/ncgen ['/usr/lib64'] > netcdf.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/ncdump ['/usr/lib64'] > netcdf.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/ncgen3 ['/usr/lib64'] > > -- > Orion Poplawski > Technical Manager 303-415-9701 x222 > NWRA/CoRA Division FAX: 303-415-9702 > 3380 Mitchell Lane address@hidden > Boulder, CO 80301 http://www.cora.nwra.com > > Howdy Orion! I am taking another pass at the configure.ac and Makefile.am files to simplify, standardize, and cut out the clutter. The idea is to make it easier to maintain, support, and also to have it seemlessly build and test windows DLL on my linux box. I will be checking in some changes to the main trunk, and they will start showing up in the main snapshot release later this week. I will make sure that I have the latest libtool before doing that... Thanks, Ed Ticket Details =================== Ticket ID: BVL-677462 Department: Support netCDF Priority: Emergency Status: Closed