> Unidata netCDF Support a Ãcrit : > > Ok, at this point, the simplest solution is for you to switch > > to the current netcdf snapshot at this url: > > ftp://ftp.unidata.ucar.edu/pub/netcdf/snapshot/netcdf-4-daily.tar.gz > > > Hi, > > Tested the daily snapshot snapshot2010092920. It works. > Except during installation > > make install gives > $ make install > Making install in include > make[1]: Entering directory > `/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include' > make[2]: Entering directory > `/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include' > make[2]: Nothing to be done for `install-exec-am'. > test -z > "/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include" > || /bin/mkdir -p > "/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include" > /usr/bin/install -c -m 644 netcdf.h > '/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include' > /usr/bin/install: `netcdf.h' and > `/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include/netcdf.h' > are the same file > make[2]: *** [install-includeHEADERS] Error 1 > make[2]: Leaving directory > `/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory > `/home/webservices/test_ferret/netcdf-4.1.2-beta2-snapshot2010092920/include' > make: *** [install-recursive] Error 1 > > Attached the full log from > $ make -d install OK, now I see what is going on. You are installing right on top of your build directory. I am not even sure that is supposed to work. It is more typical to install somewhere else (and then delete the build directory when you are done). Can you install it somewhere else as a workaround, and I will see if there is a way to do what you are trying to do? Thanks, Ed Ticket Details =================== Ticket ID: DOE-704686 Department: Support netCDF Priority: Critical 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.