Hi Thomas, > I attached the output from 'configure', 'make', and 'make check'. The > error seems to involve the doxygen program trying to access a file that > does not exist. The error message (which appears in the 'make' and 'make > check' output) is to the effect: > > </home/twalker/netcdf-4.2/netcdf-4.2/man4/tutorial.doc>:3: Warning: > included file /home/twalker/netcdf-4.2/netcdf-4.2/man4/tutorial.doc is not > found. Check your EXAMPLE_PATH > Could not open file > /home/twalker/netcdf-4.2/netcdf-4.2/man4/html//home/twalker/netcdf-4.2/netcdf-4.2/man4/tutorial.doc.html > for writing > make[3]: *** [doxyfile.stamp] Error 1 > make[3]: Leaving directory `/home/twalker/netcdf-4.2/netcdf-4.2/man4' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/home/twalker/netcdf-4.2/netcdf-4.2/man4' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/twalker/netcdf-4.2/netcdf-4.2' > make: *** [all] Error 2 You've encountered a bug in the netCDF-4.2 distribution, which shouldn't try to generate local documentation with the doxygen program unless specifically requested with an --enable-doxygen configure option. Generating the doxygen documentation is the last thing "make check does", so since you've gotten that far, you can just run "make install" and the installation will complete, possible with another error when it tries to install the doxygen-generated documentation locally. Alternatively, you could start all over and specify "--disable-doxygen" as a configure option and everything should complete without error. This problem will be fixed in the upcoming 4.2.1 release ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: SIQ-785064 Department: Support netCDF Priority: Normal 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.