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

[netCDF #XXN-300614]: nf_open_ undefined in 32 bit version (OK in 64 bit version)

Hi Chris,

> Looks like I'm almost there, just failing one test now (due to server 
> down???). Should I be concerned or am I good to go???

NetCDF version 4.2 used an operational server for testing that turned out to
cause problems, so it was changed to a dedicated test server in versions after 
4.2.0 (yes, that's actually after 4.2), including the current release 4.2.1.1.

So if that's your only problem, you probably should not be concerned.  If you
want clean output from "make check" with netCDF version 4.2, you can specify
the configure option "--disable-dap-remote-tests".

--Russ

> PASS: test_vara
> Cannot locate test server
> FAIL: test_partvar
> *** Test: varm on URL: 
> http://motherlode.ucar.edu/thredds/dodsC/testdods/coads_climatology.nc
> *** Testing: stride case 1
> *** Pass: stride case 1
> *** Testing: stride case 2
> *** Pass: stride case 2
> *** Testing: stride case 3
> *** Pass: stride case 3
> PASS: test_varm3
> *** Test: var conversions on URL: 
> file:///root/build/netcdf-4.2.1.1/ncdap_test/testdata3/test.02
> *** testing: ch_data
> *** testing: int8_data
> *** testing: uint8_data
> *** testing: int8toint32_data
> *** testing: int82float32_data
> *** testing: int16_data
> *** testing: int16toint32_data
> *** testing: int162float32_data
> *** testing: int32_data
> *** testing: int32tofloat32_data
> *** testing: int32toilong_data
> *** testing: float32_data
> *** testing: float64_data
> PASS: t_dap3a
> ================================================
> 1 of 8 tests failed
> Please report to address@hidden
> ================================================
> make[4]: *** [check-TESTS] Error 1
> make[4]: Leaving directory `/root/build/netcdf-4.2.1.1/ncdap_test'
> make[3]: *** [check-am] Error 2
> make[3]: Leaving directory `/root/build/netcdf-4.2.1.1/ncdap_test'
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory `/root/build/netcdf-4.2.1.1/ncdap_test'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/root/build/netcdf-4.2.1.1/ncdap_test'
> make: *** [check-recursive] Error 1
> 
> Thanks for your help!
> Chris
> 
> ________________________________
> From: Chris Becker
> Sent: Friday, August 24, 2012 2:20 PM
> To: address@hidden
> Subject: RE: [netCDF #XXN-300614]: nf_open_ undefined in 32 bit version (OK 
> in 64 bit version)
> 
> OK, progress, I can now generate the correct symbols!!! ...but only some 
> tests pass the check:
> 
> I'm able to generate the correct symbols by using the -fno-automatic fortran 
> option when compiling CentOS5 and CentOS6 32 bit libraries, however, CentOS5 
> fails some of the tests (CentOS6 OK):
> 
> *** Testing netCDF-3 Fortran 77 API.
> NetCDF version: 4.2.1.1 of Aug 22 2012 20:22:12 $
> *** testing nf_strerror ...
> *** testing nf_open ...
> *** testing nf_close ...
> *** testing nf_inq ...
> *** testing nf_inq_dimid ...
> *** testing nf_inq_dim ...
> *** testing nf_inq_dimlen ...
> *** testing nf_inq_dimname ...
> *** testing nf_inq_varid ...
> *** testing nf_inq_var ...
> *** testing nf_inq_natts ...
> *** testing nf_inq_ndims ...
> *** testing nf_inq_nvars ...
> *** testing nf_inq_unlimdim ...
> *** testing nf_inq_format ...
> *** testing nf_inq_vardimid ...
> *** testing nf_inq_varname ...
> *** testing nf_inq_varnatts ...
> *** testing nf_inq_varndims ...
> *** testing nf_inq_vartype ...
> *** testing nf_get_var1_text ...
> *** testing nf_get_var1_int1 ...
> *** testing nf_get_var1_int2 ...
> *** testing nf_get_var1_int ...
> *** testing nf_get_var1_real ...
> *** testing nf_get_var1_double ...
> *** testing nf_get_var_text ...
> *** testing nf_get_var_int1 ...
> *** testing nf_get_var_int2 ...
> *** testing nf_get_var_int ...
> *** testing nf_get_var_real ...
> *** testing nf_get_var_double ...
> *** testing nf_get_vara_text ...
> *** testing nf_get_vara_int1 ...
> *** testing nf_get_vara_int2 ...
> *** testing nf_get_vara_int ...
> *** testing nf_get_vara_real ...
> *** testing nf_get_vara_double ...
> *** testing nf_get_vars_text ...
> *** testing nf_get_vars_int1 ...
> *** testing nf_get_vars_int2 ...
> *** testing nf_get_vars_int ...
> *** testing nf_get_vars_real ...
> *** testing nf_get_vars_double ...
> *** testing nf_get_varm_text ...
> *** testing nf_get_varm_int1 ...
> *** testing nf_get_varm_int2 ...
> *** testing nf_get_varm_int ...
> *** testing nf_get_varm_real ...
> *** testing nf_get_varm_double ...
> *** testing nf_get_att_text ...
> *** testing nf_get_att_int1 ...
> *** testing nf_get_att_int2 ...
> *** testing nf_get_att_int ...
> *** testing nf_get_att_real ...
> *** testing nf_get_att_double ...
> *** testing nf_inq_att ...
> *** testing nf_inq_attname ...
> *** testing nf_inq_attid ...
> *** testing nf_inq_attlen ...
> *** testing nf_inq_atttype ...
> *** testing nf_create ...
> *** testing nf_redef ...
> *** testing nf_enddef ...
> *** testing nf_sync ...
> *** testing nf_abort ...
> *** testing nf_def_dim ...
> *** testing nf_rename_dim ...
> *** testing nf_def_var ...
> *** testing nf_put_var1_text ...
> *** testing nf_put_var1_int1 ...
> *** testing nf_put_var1_int2 ...
> *** testing nf_put_var1_int ...
> *** testing nf_put_var1_real ...
> *** testing nf_put_var1_double ...
> *** testing nf_put_var_text ...
> *** testing nf_put_var_int1 ...
> *** testing nf_put_var_int2 ...
> *** testing nf_put_var_int ...
> *** testing nf_put_var_real ...
> *** testing nf_put_var_double ...
> *** testing nf_put_vara_text ...
> *** testing nf_put_vara_int1 ...
> *** testing nf_put_vara_int2 ...
> *** testing nf_put_vara_int ...
> *** testing nf_put_vara_real ...
> *** testing nf_put_vara_double ...
> *** testing nf_put_vars_text ...
> *** testing nf_put_vars_int1 ...
> *** testing nf_put_vars_int2 ...
> *** testing nf_put_vars_int ...
> *** testing nf_put_vars_real ...
> *** testing nf_put_vars_double ...
> *** testing nf_put_varm_text ...
> *** testing nf_put_varm_int1 ...
> *** testing nf_put_varm_int2 ...
> *** testing nf_put_varm_int ...
> *** testing nf_put_varm_real ...
> *** testing nf_put_varm_double ...
> *** testing nf_rename_var ...
> *** testing nf_put_att_text ...
> *** testing nf_put_att_int1 ...
> *** testing nf_put_att_int2 ...
> *** testing nf_put_att_int ...
> *** testing nf_put_att_real ...
> *** testing nf_put_att_double ...
> *** testing nf_copy_att ...
> *** testing nf_rename_att ...
> *** testing nf_del_att ...
> *** testing nf_set_fill ...
> *** testing nf_set_default_format ...
> Total number of failures:            0
> *** SUCCESS!
> PASS: nf_test
> 
> *** Copying file with fill values.
> *** SUCCESS!
> PASS: create_fills.sh
> 
> *** Testing netCDF v2 api for F77.
> *** SUCCESS!
> PASS: tst_f77_v2
> 
> *** Testing definition of netCDF-4 vars from Fortran 77.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_vars
> 
> *** Testing netCDF-4 vars from F77 with new types.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_vars2
> 
> *** Testing enum and opaque types.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_vars3
> 
> *** Testing VLEN types.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_vars4
> 
> *** Testing compound types.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_vars5
> 
> *** Testing fill values.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_vars6
> 
> *** Testing netCDF-4 compound type from F77.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_types
> 
> *** Testing netCDF-4 compound types from F77 some more.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_types2
> 
> *** Testing netCDF-4 user-defined types and groups.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_types3
> 
> *** Testing netCDF-4 groups from F77.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: ftst_groups
> 
> *** Testing definition of netCDF-4 vars from Fortran 90.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: f90tst_vars
> 
> *** Testing new netCDF-4 types from Fortran 90.
> NetCDF: Unknown file format
> STOP 2
> FAIL: tst_types
> 
> *** Testing netCDF-4 64-bit integer types from Fortran 90.
> NetCDF: Unknown file format
> STOP 2
> FAIL: tst_types2
> PASS: f90tst_vars_vlen
> 
> *** testing simple netCDF-4 file.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: tst_f90_nc4
> 
> *** Testing netCDF-4 groups from Fortran 90.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: f90tst_grps
> 
> *** Testing netCDF-4 fill values.
> Error: NetCDF: Unknown file format
> STOP 99
> FAIL: f90tst_fill
> 
> *** Testing netCDF-4 fill values with unlimited dimension.
> Error: NetCDF: Unknown file format
> STOP 99
> FAIL: f90tst_fill2
> 
> *** Testing definition of netCDF-4 vars from Fortran 90.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: f90tst_vars3
> 
> *** Testing definition of netCDF-4 vars from Fortran 90.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: f90tst_vars4
> 
> *** Testing definition of netCDF-4 vars from Fortran 90.
> Error: NetCDF: Unknown file format
> STOP 2
> FAIL: f90tst_vars2
> 
> *** Testing v2 fortran API with netCDF-4.
> ncopen: filename "ftst_v2.nc": NetCDF: Unknown file format
> FAIL: ftst_v2
> 
> *** Testing netCDF-2 Fortran 77 API.
> *** testing nccre ...
> *** testing ncddef ...
> *** testing ncvdef ...
> *** testing ncapt, ncaptc ...
> *** testing ncclos ...
> *** testing ncvpt1 ...
> *** testing ncvgt1 ...
> *** testing ncvpt ...
> *** testing ncopn, ncinq, ncdinq, ncvinq, ncanam, ncainq ...
> *** testing ncvgt, ncvgtc ...
> *** testing ncagt, ncagtc ...
> *** testing ncredf, ncdren, ncvren, ncaren, ncendf ...
> *** testing ncacpy ...
> *** testing ncadel ...
> *** testing fill values ...
> Total number of failures:            0
> *** SUCCESS!
> PASS: ftest
> 
> *** Testing netCDF-3 Fortran 90 API.
> *** SUCCESS!
> PASS: tst_f90
> ================================================
> 21 of 27 tests failed
> Please report to address@hidden
> ================================================
> make[2]: *** [check-TESTS] Error 1
> make[2]: Leaving directory `/root/build/netcdf-fortran-4.2/nf_test'
> make[1]: *** [check-am] Error 2
> make[1]: Leaving directory `/root/build/netcdf-fortran-4.2/nf_test'
> make: *** [check-recursive] Error 1
> 
> Thanks for your help,
> Chris
> 
> ________________________________
> From: Chris Becker
> Sent: Friday, August 24, 2012 1:08 PM
> To: address@hidden
> Subject: RE: [netCDF #XXN-300614]: nf_open_ undefined in 32 bit version (OK 
> in 64 bit version)
> 
> Thanks Guys,
> 
> Here's an update: nf_open_ undefined in 32 bit version of CentOS5 only (OK in 
> 64 bit CentOS5, 64 bit CentOS6, 32 bit CentOS6)
> 
> I was able to get the right symbol generation in 32 bit CentOS6 by adding 
> -DgFortran to CPPFLAGS|CFLAGS. This, unfortunately, did not seem to work for 
> 32 bit CentOS5. I even tried the -fno-second-underscore fortran flags to no 
> avail.
> 
> Here is my 32 bit config delta for CentOS6 vs CentOS5 (perhaps this will 
> help):
> 
> ? diff config.CentOS6.32bit config.CentOS5.32bit
> 53c53
> < checking the maximum length of command line arguments... 1966080
> ---
> > checking the maximum length of command line arguments... 98304
> 79c79
> < checking if gcc static flag -static works... no
> ---
> > checking if gcc static flag -static works... yes
> 95c95
> < checking if gfortran -m32 static flag -static works... no
> ---
> > checking if gfortran -m32 static flag -static works... yes
> 106c106
> < checking if gfortran -m32 static flag -static works... no
> ---
> > checking if gfortran -m32 static flag -static works... yes
> 116c116
> < checking for _FILE_OFFSET_BITS value needed for large files... 64
> ---
> > checking for _FILE_OFFSET_BITS value needed for large files... no
> 146c146
> < checking for oc_open... no
> ---
> > checking for oc_open... yes
> 
> BTW, I tried to boost CentOS5 large file support (like I see in CentOS6) by 
> adding -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 flags but this did not 
> change the output of CentOS5 configuration command.
> 
> Anyway, I'll let you know if I make any progress at this end.
> 
> Thanks,
> Chris
> ________________________________________
> From: Unidata netCDF Support [address@hidden]
> Sent: Friday, August 24, 2012 12:18 PM
> To: Chris Becker
> Subject: [netCDF #XXN-300614]: nf_open_ undefined in 32 bit version (OK in 64 
> bit version)
> 
> address@hidden,
> 
> Your Ticket has been received, and a Unidata staff member will review it and 
> reply accordingly. Listed below are details of this new Ticket. Please make 
> sure the Ticket ID remains in the Subject: line on all correspondence related 
> to this Ticket.
> 
> Ticket ID: XXN-300614
> Subject: nf_open_ undefined in 32 bit version (OK in 64 bit version)
> Department: Support netCDF
> Priority: Normal
> Status: Open
> 
> 
> 
> The NetCDF libraries are developed at the Unidata Program Center/UCAR,
> in Boulder, Colorado; we are funded primarily by the U.S. National
> Science Foundation.
> 
> All support requests are handled by the development team; no
> dedicated support staff are funded at this time. For this reason
> we cannot guarantee response times, nor can we resolve every support
> issue, although we do our best to respond within 72 hours.
> 
> It is in the nature of support requests that the same question is
> asked many times. We urge you to search the support archives for
> material relating to your support inquiry:
> 
> http://www.unidata.ucar.edu/search.jsp?support&netcdf
> 
> If you are having trouble building netCDF, please take a look at the
> "Build Troubleshooter" section of the netCDF home page:
> 
> http://www.unidata.ucar.edu/software/netcdf/
> 
> Windows users should see the FAQ list:
> 
> http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#windows_netcdf4
> 
> Complete documentation (including a tutorial, and sample programs in
> C, Fortran, Java, and other programming languages) can be found on the
> netCDF Documentation page:
> 
> http://www.unidata.ucar.edu/software/netcdf/docs/
> 
> If you resolve your issue through one of these methods, please send a
> reply to this email letting us know that you no longer require
> assistance. This will help us spend more time on netCDF development.
> 
> Best regards,
> 
> Unidata User Support
> 
> 
> 
> 
Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: XXN-300614
Department: Support netCDF
Priority: Normal
Status: Closed