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.
Thanks Richard. Actually I'm using configure and gmake. You (or anyone out there :>) wouldn't happen to know what the configure option is to turn off the "makeinfo" call would youl thanks, Steve On Wed, Jul 2, 2014 at 12:06 PM, Richard Weed <rweed@xxxxxxxxxxxxxxxx> wrote: > Steve > > I think there is a configure option to bypass this. I'm not sure > about CMake if thats what you are using. Also, unless you are trying > to build on a Windows platform (the main reason for CMake builds), I would > advise you try building with configure instead of CMake. I don't think the > CMake procedure is completely stable yet. > > RW > > > On 07/02/2014 12:24 PM, steve kirby wrote: > >> Richard, >> >> Sorry for the delay in responding - was testing. Thanks for the code >> suggestions. I used them and got past the CINT1/CINT2 problem. >> >> Now I'm seeing: >> >> makeinfo: command not found >> WARNING: 'makeinfo' is missing on your system. >> You should only need it if you modified a '.texi' file, or >> any other file indirectly affecting the aspect of the manual. >> You might want to install the Texinfo package: >> <http://www.gnu.org/software/texinfo/> >> The spurious makeinfo call might also be the consequence of >> using a buggy 'make' (AIX, DU, IRIX), in which case you might >> want to install GNU make: >> <http://www.gnu.org/software/make/> >> gmake[2]: *** [netcdf-f90.info <http://netcdf-f90.info>] Error 127 >> >> >> Is there an easy way to turn off this part of the make? (would be easier >> than >> trying to install makeinfo) >> >> Also, and I don't know if it is related to this (since the make isn't >> finishing), in /fortran/.libs, there is no libnetcdff.so.0.0.0 and this >> is what >> libnetcdff.so and libnetcdff.so.0 point to. >> >> --Steve >> >> >> On Tue, Jul 1, 2014 at 1:06 PM, Richard Weed <rweed@xxxxxxxxxxxxxxxx >> <mailto:rweed@xxxxxxxxxxxxxxxx>> wrote: >> >> Also, >> >> this indicates there might be a problem with the Cmake >> and/or configure scripts with gcc 4.9. >> >> And on second thought it might be better to make the default >> values the corresponding 1 and 2 byte values instead of >> the 4 byte vals. >> >> RW >> >> On 07/01/2014 01:30 PM, Richard Weed wrote: >> >> This indicates that the NF_INT1_IS and NF_INT2_IS cpp macros >> have not been defined in nfconfig.inc or are null >> >> I probably should have added defaults to the #ifdefs in >> module_netcdf_nc_data.F90 but this is the first time this >> has ever come up. >> >> Try the following >> >> after >> >> #elif NF_INT1_IS_C_LONG >> Integer, Parameter :: CINT1 = C_LONG >> Integer, Parameter :: NFINT1 = IK8 >> >> and before the #endif insert >> #else >> Integer, Parameter :: CINT1 = C_INT >> Integer, Parameter :: NFINT1 = IK4 >> >> similar logic for the CINT2 values >> #else >> Integer, Parameter :: CINT2 = C_INT >> Integer, Parameter :: NFINT2 = IK4 >> >> >> Russ, can you add these to the current github repository >> >> RW >> >> On 07/01/2014 10:25 AM, steve kirby wrote: >> >> Hi, >> >> I'm trying to compile netcdf-fortran-4.4b5 and get errors >> like this >> for both >> CINT1 and CINT2. I'm using gcc version 4.9.0 >> >> ==============================__=========================== >> module_netcdf_nc_interfaces.__f90:647.26: >> >> >> USE NETCDF_NC_DATA, ONLY: CINT1 >> 1 >> Error: Symbol 'cint1' referenced at (1) not found in module >> 'netcdf_nc_data' >> module_netcdf_nc_interfaces.__f90:650.14: >> >> Integer(KIND=CINT1), Intent(IN) :: op(*) >> ==============================__=========================== >> >> 1 >> Error: Parameter 'cint1' at (1) has not been declared or is a >> variable, which >> does not reduce to a constant expression >> >> Also note that I built the netCDF "C" portion first, >> netcdf-4.3.0. >> >> Thanks for any tips/ideas on how to resolve this. >> >> Regards, >> Steve >> >> >> _________________________________________________ >> netcdfgroup mailing list >> netcdfgroup@xxxxxxxxxxxxxxxx <mailto:netcdfgroup@unidata. >> ucar.edu> >> >> For list information or to unsubscribe, visit: >> http://www.unidata.ucar.edu/__mailing_lists/ >> >> <http://www.unidata.ucar.edu/mailing_lists/> >> >> >> >> -- >> --- >> ----- >> >> Richard Weed, Ph.D. >> Associate Research Professor >> Center for Advanced Vehicular Systems (CAVS) >> Mississippi State University >> >> email: rweed@xxxxxxxxxxxxxxxx <mailto:rweed@xxxxxxxxxxxxxxxx> >> Phone: (662) 325-5450 <tel:%28662%29%20325-5450> >> >> >> > -- > --- > ----- > > Richard Weed, Ph.D. > Associate Research Professor > Center for Advanced Vehicular Systems (CAVS) > Mississippi State University > > email: rweed@xxxxxxxxxxxxxxxx > Phone: (662) 325-5450 >
netcdfgroup archives: